[prev in list] [next in list] [prev in thread] [next in thread] 

List:       antlr-interest
Subject:    [antlr-interest] Implementing Preprocessor Functions
From:       ewbank () gmail ! com (Bryan Ewbank)
Date:       2006-02-24 12:14:05
Message-ID: dd3a065f0602241214j181a8b4as80a36a07a471e5ef () mail ! gmail ! com
[Download RAW message or body]

If there's really a need for a meta-language (why aren't existing flow
control good enough?)...

Rather than "similar to C++'s preprocessor", why not just preprocess
with "gcc -E" to use the C++ preprocessor.  That way, you don't need
to match an existing implementation, nor document your new language.

This model makes a firewall between the preprocessor and the
scanner/parser as well.

The only problem I've had with this model is some of the edge cases
around character literals and string processing...

On 2/22/06, de Jong, Ron <ron@iesys.com.au> wrote:
> to the C++ #include, #ifdef, #else, #endif, #define....

[prev in list] [next in list] [prev in thread] [next in thread]