Re: too many warnings from Bison CVS for Pike

[Paul Eggert]

Hans Aberg <address@hidden> writes:

> when people compile your C-parser using a C++ compiler, they are
> not compiling C-code actually,

If they are not compiling C source code, then it's up to them to get
things to work.  yacc.c is designed for C source code.  It does not
work well with C++ source code, and we shouldn't recommend it for
that.

> but a C-like language subset of C++
> that can be linked to proper C-code at need.

If the user wants to use different C compilers for different parts of
the application, it's up to them to get things to work.  This is true
for random combinations of C compilers; it's also true for C++
compilers masquerading as C compilers (which are just special cases of
C compilers).  We shouldn't need to document all the issues here.
They are generic issues, and are not specific to Bison.  Anybody who
wants to mix C compilers should know what they're doing anyway; it's
not the Bison documentation's job to educate them.

I don't sense that we are making much progress here.  It would help if
you would propose specific patches, in "diff -u" format.  Otherwise I
fear that we are just going around in circles.