Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] decoupled preprocessor

Yes, it is definitely something I'll need. I'll need to take a look at what
you've done. ANTLR uses it's own character stream interface to feed
characters to the lexer. It provides implementations that can pull that out
of Readers and InputStreams. I will likely want to create a new one that
doesn't try to load it all into a char[] at startup like the built in ones
do. We can then hook that up to the preprocessor.

I'm not sure how you built yours but the easiest path I can see is to take
our current scanner and replace nextToken with getChar and strip out
anything that creates a token. But if you already have everything we've done
there, then might be the better approach.

Anyway, another shiny object flew by called CDT user docs, so I'll get back
to ANTLR in a few days :).

Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead,

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Mike Kucera
> Sent: Tuesday, June 19, 2007 3:43 PM
> To: CDT General developers list.
> Subject: [cdt-dev] decoupled preprocessor
> Hi Doug,
> I take it from your latest blog post that you are going to be in need of a
> preprocessor for you ANTLR C++ experiment. I was planning on decoupling
> the
> preprocessor that I wrote for the C99 parser so that it can be used with
> any parser. If you are interested in picking this up when would you need
> it?
> Mike Kucera
> Software Developer
> IBM CDT Team, Toronto
> mkucera@xxxxxxxxxx
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx

Back to the top