Re: %destructor feedback

[Joel E. Denny]

On Fri, 23 Dec 2005, Akim Demaille wrote:

> > I noticed you're not defining any sort of public YYUSE.  Leaving it up to
> > the user is fine with me.  Is this your long term plan, or have you just
> > not dealt with it yet?
> 
> I was hoping someone would come with the final suggestion :)
> So are we suggesting YYUSE, or introduce another empty macro?

Providing the user with macros to combat compiler and lint warnings in 
user code doesn't seem like a job that bison should take on.  However, 
providing the user with macros to combat bison warnings does.  Thus, I 
still vote that these should be distinct macros with distinct purposes.

If you and Paul decide that making the internal YYUSE public is the right 
way to go, I'll defer, and it won't cause me any trouble. I'm just glad 
Paul got the internal YYUSE working so well. :)

Joel