Hello Alexander,
If the "documented" compiler directive variable isn't working, I would just
make my own so I only had to change one of code:
{$DEFINE USEINLINE}
{$INFO ============= }
{$IFDEF USEINLINE}
{$INFO COMPILING WITH INLINE }
{$ELSE}
{$INFO COMPILING WITHOUT INLINE }
{$ENDIF}
I have some code that has been commented as being very interesting for the
compiler directives alone: http://www.jegas.org/?PAGE=main&SECTION=download
Try compiling test_uxxc_console.pas for example. You should do this at the
command prompt so the compile window doesn't disappear on you or anything.
But NOTE: I use the += syntax, so you either have to add that construct to
Your fp.cfg (or whatever file it is) or compile using the -Sc switch on the
command line. (Enables += *= etc... which I use heavily)
I use conditional defines and {$INFO Blah blah} statements heavily - and it
Comes in handy for dumping compile output to text files and searching for
things - to see how a binary was compiled etc.
I hope this answers at least one of your questions.
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.6/646 - Release Date: 1/23/2007
3:36 AM
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
