> Am 20.06.2018 um 12:00 schrieb fpc-pascal-requ...@lists.freepascal.org: > > Date: Wed, 20 Jun 2018 16:25:39 +0700 > From: Ryan Joseph <r...@thealchemistguild.com> > To: FPC-Pascal users discussions <fpc-pascal@lists.freepascal.org> > Subject: Re: [fpc-pascal] Proper preprocessor? > Message-ID: <d900f179-f2ae-49c1-9d1d-ef7ab1296...@thealchemistguild.com> > Content-Type: text/plain; charset=utf-8 > > How does an external preprocessor work if the compiler doesn’t about it? > Doesn’t it totally mess up the line numbers for debugging?
If the preprocessor really does such extended work, can't one simply keep the intermediate output of the preprocessor as a source file and then relate to that? I did quite some work in transposing C header files to Pascal. Most of the defines could simply be converted into const statements by h2pas. For more elaborate stuff, like versions of installed C libs and such, the usual tools known C programming (m4, configure, …) can be used (Ultrastar Deluxe has quite some use of them), as already mentioned by Michael Van Canneyt. Due to their complexity, I would avoid them as much as possible. My 2 cents - MiSchi.
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
