Marco van de Voort wrote:
In our previous episode, Mark Morgan Lloyd said:
Unfortunately pascal macro's are rather limited compared to C. I know I know,
you could potentially open up a can of worms, but sometimes more control is
required.
There is nothing restraining anybody using an external macro processor. It
is just that we don't want to support it :-)
Actually, I'd suggest that there is: the difficulty of integrating an
external macro processor with the standard build process (i.e. it's not
just another stage in a makefile).
It is. Export all known sources to a new dir for the compiler through the
preprocessor.
I meant that in the context of FPC, which works out dependencies etc. on
the fly, one can't arbitrarily hook in an external preprocessor. I meant
that it wasn't another stage in a makefile because FPC doesn't (can't)
use makefiles- for reasons that you explained yesterday.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
