merging cccp and cpplib

Paul Eggert eggert@twinsun.com
Sun Dec 6 13:52:00 GMT 1998


   Date: Sun, 6 Dec 1998 14:02:48 +0100
   From: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>

   Wouldn't it be better to drop cccp alltogether in favour of cpplib?

That's basically the idea, yes.  But unfortunately, the last time I
checked, the cpplib-based preprocessor was considerably slower than
the cccp.c version.  I'd like to revamp the code so that there
wouldn't be such a performance problem.  (Warning: this might affect
the cpplib interface somewhat, though I don't want to make gratuitous
changes.)

Also, I should confess that the cpplib code has some minor bugs that
the cccp code doesn't, due to laziness on my part.  For some time I've
planned to start with the cccp code and re-cpplibize it (addressing
the performance concerns mentioned above), and with this in mind I
haven't bothered to fix some relatively unimportant bugs in cpplib.
Hence I think the cccp.c code is the right one to start with.

I've been holding off on this because I wanted to implement C9x while
I was at it, and the C9x drafts kept changing the preprocessing rules.
But C9x seems to be settling down, so it might be time to start hacking soon.



More information about the Gcc-bugs mailing list