[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: too many warnings from Bison CVS for Pike

From: Hans Aberg
Subject: Re: too many warnings from Bison CVS for Pike
Date: Mon, 6 Feb 2006 13:45:15 +0100

On 6 Feb 2006, at 09:55, Akim Demaille wrote:

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

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

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.

I must have misremembered it, because my memory said it was dropped. Good that you clarify the issue. It is good to have this kind of limited C++ support, because some programs do this feature.

  Hans Aberg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]