This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: New Cpp not right for non-C files


I thought we had solved this by using the actual old preprocessor
for -traditional?

Zack Weinberg wrote:
> 
> On Thu, Jul 27, 2000 at 01:22:28PM +1000, Anthony Thyssen wrote:
> > For a very long time I have been using the C-preprocessor for
> > large scale documention control. EG: I create a document with
> > various CPP #ifdef #endif controls so I can then use cpp to
> > generate from the single source a large number of slightly different
> > files. The point is a single source for all the docimentation
> 
> Sorry.  The preprocessor is designed to work with C, C++, and
> Objective C.  We also support using it with assembly language,
> Fortran, Chill, and - under protest! - Makefiles, but those are only
> for backward compatibility with huge established bases of code.
> Arbitrary text is most definitely not supported.
> 
> We suggest you use a real general-purpose macro preprocessor, such as
> M4, instead.
> 
> zw

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]