[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: Joel E. Denny
Subject: Re: too many warnings from Bison CVS for Pike
Date: Sat, 25 Feb 2006 19:10:23 -0500 (EST)

On Wed, 22 Feb 2006, Akim Demaille wrote:

> Le 21 f?vr. 06 ? 19:34, Joel E. Denny a ?crit :
> > Section `10.1.2 C++ Semantic Values' explains that only *pointers* to
> > non-POD types can be used in %union for "lalr1.cc" and that %destructor is
> > needed to prevent memory leaks.
> That's because we are using a union underneath.  So we inherit
> the same limitations.

I actually understood this point.  I was setting up for my question as to 
whether there's some problem with doing the same when using "yacc.c" (or 
"glr.c").  It seems the answer is basically no.

> Yes.  Supporting non-PODs is really tough to do properly.  We need
> something like Boost's variants.

Thanks for the references.  It's an interesting and complex issue.  
However, I need more experience using bison's C++ skeletons before I'm 
competent to continue this discussion.


reply via email to

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