On Friday 01 October 2010 19:33:48 Mark Daems wrote:
> ...
> And it's a weird behaviour, because it's all within an {$IFDEF FPC}
> construct. Why does delphi even try to interprete it?
> 
> Somebody knows how to avoid the problem?

Try this instead:

{$IFNDEF FPC}
  // Can be empty
{$ELSE}
  ...
{$ENDIF}

I got feedback for the Delphi converter in Lazarus about this same problem.
Now the converter always adds IFNDEF instead of IFDEF to the code.

Juha
_______________________________________________
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Reply via email to