Related articles |
---|
implementing #include etc without pre-preprocessing sfrederi@asc.corp.mot.com (Sudhakar Frederick) (1997-03-16) |
Re: implementing #include etc without pre-preprocessing thetick@scruz.net (Scott Stanchfield) (1997-03-18) |
Re: implementing #include etc without pre-preprocessing bothner@cygnus.com (1997-03-21) |
Re: implementing #include etc without pre-preprocessing ftit07bv85@pop.anti.wanadoo.spam.fr (1997-03-21) |
Re: implementing #include etc without pre-preprocessing ok@cs.rmit.edu.au (1997-03-21) |
Re: implementing #include etc without pre-preprocessing sethml@ugcs.caltech.edu (1997-03-22) |
From: | bothner@cygnus.com (Per Bothner) |
Newsgroups: | comp.compilers |
Date: | 21 Mar 1997 10:11:26 -0500 |
Organization: | Cygnus Solutions, CA |
References: | 97-03-090 |
Keywords: | parse |
Sudhakar Frederick <sfrederi@asc.corp.mot.com> wrote:
>Is it practical to implement "conditional compilation" C-style
>constructs similar to #include, #define #ifdef etc. as part of the
>parsing rather than through a pre-processor.
I wrote "cpplib" which is a package for doing cpp-style processing.
The package includes cppmain, a simple driver that replaces cpp.
Cpplib is included with the gcc sources, but is currently only used
for fix-proto. The long -term goal is for cppmain to replace cpp, and
the gcc and g++ lexers to call cpplib directly; however, no-one has
had time to do the "last 10%" of the work.
--
--Per Bothner
Cygnus Solutions bothner@cygnus.com http://www.cygnus.com/~bothner
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.