> |{$IFNDEF MSWINDOWS}
> {$IFNDEF FPC}
> Libc,
> {$ELSE}
> {$IFDEF FPC_USE_LIBC}
> Libc,
> {$ENDIF}
> {$ENDIF}
> {$ELSE}
> Windows,
> {$ENDIF}
> SysUtils,
> synautil, synacode, synaicnv;|
The FPC_USE_LIBC clause is wrong. That directive governs FPC's own Unix
libraries to base on /library/ libc.
However that has nothing to do with /unit/ libc, which is Kylix legacy.
If FPC uses library libc, it is not through unit libc.
In short, proper FPC code should never use /unit/ libc. If you need *nix
specific types, use baseunix,unix
See
http://wiki.freepascal.org/libc_unit
> Also, as Petr mentioned, there are some obsolete warnings regarding the
> FormatSettings in some of the units (as he mentioned)
FPC 2.6.0+ afaik also gives those warnings. That change was btw already
introduced with Delphi XE, not XE2.
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
synalist-public mailing list
synalist-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synalist-public
