Re: too many warnings from Bison CVS for Pike

[Akim Demaille]

>>> "Hans" == Hans Aberg <address@hidden> writes:

 >> Or do you simply mean the ability to compile the generated C as
 >> C++?

 > Instead, the C parser was for some time unofficially written so that
 > some could compile it using a C++ compiler. But then C++ added
 > namespaces, which in combination with other things (like the need for
 > invoking the copy constructors during a parser stack extension), made
 > it difficult to maintain. So this idea of being able compile the C
 > parser as C++ was dropped, though some projects are using it (perhaps
 > LilyPond is one).

I disagree with this view of Bison's history.  Indeed, we have always
fought for yacc.c to compile cleanly in C++, and we still do, but
having a C++ cleaner interface is a separate issue.