On Wed, 23 May 2001, Mike Alexander stipulated:
--On Wednesday, May 23, 2001 9:52 PM +0100 Nix
<nix(a)esperi.demon.co.uk> wrote:
> Fun. (But if this were C++ it would not be fun, it would be
> torment...)
>
Yes, I can imagine it would be. I would certainly hate to do anything
that would heavily penalize the use of C++ in XEmacs or worse yet,
make it impossible.
The CodeSourcery folks are rewriting the C++ parser into something
that's actually maintainable; when that's done I could produce a C++
variant of the preprocessor (let's give it a name: gcpp. The C++
variant would presumably be gcpppp...)
Also don't forget about the native Windows build using MSVC
while
thinking about this. Nothing you've said so far jumps out as being
impossible, but that's a rather different environment with a different
C compiler and preprocessor to worry about.
That's irrelevant; this preprocessor's not trying to compile the code,
just to pick out declarations and function calls and do a little simple
rewriting. As long as the C used in the MSVC build (and headers) isn't
gratutiously nonstandard, the parser should be happy. (And if it isn't I
can rejig it until it is; MS's changes to C can't be *that* bad, can
they? Unless they've broken block structure or declarations...)
(Aside: I'm getting a little worried by the length of this cc list...)
--
`LARTing lusers is supposed to be satisfying. This is just tedious. The
silly shite I'm doing now is like trying to toothpick to death a Black
Knight made of jelly.' --- RDD