|[13 earlier articles]|
|Re: Parsing partial sentences DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2017-04-20)|
|Re: Parsing partial sentences email@example.com (George Neuner) (2017-04-21)|
|Re: Parsing partial sentences firstname.lastname@example.org (Walter Banks) (2017-04-27)|
|Re: Parsing partial sentences email@example.com (Kaz Kylheku) (2017-04-27)|
|Re: Parsing partial sentences DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2017-04-28)|
|Re: Parsing partial sentences firstname.lastname@example.org (2017-04-28)|
|Re: Parsing partial sentences email@example.com (Marco van de Voort) (2017-04-29)|
|Re: Parsing partial sentences firstname.lastname@example.org (Kaz Kylheku) (2017-04-30)|
|From:||Marco van de Voort <email@example.com>|
|Date:||Sat, 29 Apr 2017 14:57:26 +0000 (UTC)|
|Organization:||Stack Usenet News Service|
|References:||17-04-001 17-04-023 17-04-024|
|Injection-Info:||miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="62527"; mail-complaints-to="firstname.lastname@example.org"|
|Posted-Date:||29 Apr 2017 11:02:57 EDT|
On 2017-04-27, Kaz Kylheku <email@example.com> wrote:
>> In a word NO. #defines are always strings even when they look like
>> constants, something I have found out the hard way. There have only been
>> two ways that I have successfully dealt with #defines: a preprocessor
>> pass or later and much faster pipeline the processing of C source and
>> add the defined definition processing into part of the source fetch
> If we allow Pascal to be extended with a macro preprocessor,
I think most interest in C->Pascal header translators is for (semi)automated
translation of 3rd party library headers, not converting complete programs.
This means that it cannot be considered a given that a program exists that
uses all macros in the header.
Estabilishing rules or heuristics to judge if a macro could be a constant
would be useful though.
Return to the
Search the comp.compilers archives again.