Re: too many warnings from Bison CVS for Pike

[Paul Eggert]

"Joel E. Denny" <address@hidden> writes:

> This confusion makes me wonder if %destructor really should be by type

To be honest I'm surprised it's not done by type.  However, it may
be too late to change this now.  Or perhaps we could add a new
feature %type-destructor that is by type.

> and if $<type>$ should dynamically record a new type for that state
> on the stack.

That might make sense, for %type-destructor anyway.

But it is getting a bit complicated.  It might be better just to leave
things be, and warn users that $<type>$ and destructors don't mix.
(The problem is not limited to midrule actions, no?)

Perhaps we could even issue a warning if the user combines $<type>$
with destructors.  (After 2.2 is out.)