[Top][All Lists]

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

Re: bison'd files don't compile under Microsoft VC++

From: Paul Eggert
Subject: Re: bison'd files don't compile under Microsoft VC++
Date: Thu, 14 Feb 2002 11:39:49 -0800 (PST)

> Date: Thu, 14 Feb 2002 16:02:48 +0100
> From: Hans Aberg <address@hidden>

> these developers on the one hand put off the genuine C++ issue off
> indefinitely for a long period of time (several years), while on the
> same time compiling the C parser as C++ in their own projects. Then
> one day, their own C++ projects started to break, because they got
> hold of a C++ compiler that checked the C++ code properly, catching
> errors in the earlier dirty compile C as C++ code.

I believe you're referring to the fact that Bison has never supported
C++ objects on the stack that require constructor/destructor support.
If so, the current situation is an improvement, since the newer C++
compilers now are rejecting such parsers at compile-time, rather than
having the code fail mysteriously at run-time.

This problem as far more serious than the namespace problem, since the
namespace problem is easily worked around, whereas there's often no
good substitute for having full-fledged objects on the stack.  On my
list of things to do is to fix the C parser so that it is properly
robust even in this situation.  However, this fix is not something
that I want to put into the next minor release, as it will take some
time to shake out the porting bugs.  It should wait for a major

> >The fact that Bison parsers used to work with C++ in the past is
> >more by accident than by design.
> It was actually by design, ...

What gives you that impression?  It's news to me.

reply via email to

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