<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style='font-family: Verdana,Geneva,sans-serif'>
<p>marcov@stack.nl schreef op 6 mrt '13:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<pre>In our previous episode, Mark Morgan Lloyd said:</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">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.</blockquote>
There is nothing restraining anybody using an external macro processor. It is just that we don't want to support it :-)</blockquote>
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).</blockquote>
<pre>It is. Export all known sources to a new dir for the compiler through the
preprocessor.</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">I've had to deal with colleagues in the past who thought it was entirely acceptable to make manual edits to compiler output (typically on Intel blue boxes) before running it through the assembler, and it's very high on my list of Thou Shalt Nots.</blockquote>
<pre>General preprocessor usage is on mine. I use preprocessors and
codegenerators all the time, and have no problem whatsoever with it.
What I have a problem is, is to give that formal statement, so that future
development on the compiler will be limited by it in all its gory glory.
IMHO we should simply have a directive that is either cdecl or stdcall
depending on the platform, and kill even the current macro support.
_______________________________________________
fpc-pascal maillist - <a href="mailto:fpc-pascal@lists.freepascal.org">fpc-pascal@lists.freepascal.org</a>
<a href="http://lists.freepascal.org/mailman/listinfo/fpc-pascal">http://lists.freepascal.org/mailman/listinfo/fpc-pascal</a>
</pre>
</blockquote>
<p>What preprocessor do you use then, M4? I'm curious to find out how you use an external preprocessor. In principle it's not a bad idea to use an external one. I suggest we could also make it a bit more user friendly by providing some hooks in fpmake. This way one should not nescesarily create additional scripts to copy files to other locations. What do you think?<br /><br />Please demonstrate how you use macro's in your perticular case. How do you adjust your build system.</p>
<br />
<div> </div>
</body></html>