On 28 Jul 2009, at 16:56, Bee wrote:
Rewriting the unit loading system isn't exactly a trivial task.
I understand. I just wonder why this bug didn't got priority since
it's pretty basic feature for pascal compiler.
You cannot get bugs fixed in a project like FPC by "giving them
priority".
> Rewriting the unit loading system isn't exactly a trivial task.
I understand. I just wonder why this bug didn't got priority since
it's pretty basic feature for pascal compiler.
> No idea, sorry. Maybe adding a dummy constant declaration between the uses
> clause and the {$if ...} expression wo
On 28 Jul 2009, at 16:47, Bee wrote:
The internal error is due to the fact that your {$if ...} construct
appears
right after your uses clause: http://bugs.freepascal.org/view.php?id=8611
So, it's a bug. Since 2007? :(
Rewriting the unit loading system isn't exactly a trivial task.
Thanks
> The internal error is due to the fact that your {$if ...} construct appears
> right after your uses clause: http://bugs.freepascal.org/view.php?id=8611
So, it's a bug. Since 2007? :(
Thanks for the hint. I'll find a workaround for that. Any suggestion? TIA.
--
-Bee-
...making buzzes at http:
On 28 Jul 2009, at 14:42, Bee wrote:
In another unit which uses the above unit, I want to have conditional
compilation based on the above constant...
{$IF AValue}
Do something...
{$ELSE}
Do something else...
{$IFEND}
I know it's possible in Delphi. But, is it possible in FPC? Using the
ab
Hi all,
Say I had a constant declared in a unit...
const
AValue = true;
In another unit which uses the above unit, I want to have conditional
compilation based on the above constant...
{$IF AValue}
Do something...
{$ELSE}
Do something else...
{$IFEND}
I know it's possible in Delphi. Bu
