Re: Another - Bison 1.35 works but Bison 1.50 Doesn't

[Akim Demaille]

>>>>> "Tim" == Tim Van Holder <address@hidden> writes:

Tim> OTOH, without the warning, a memory leak is introduced if the
Tim> semantic value is dynamically allocated.  With the warning, it
Tim> can be easily found & fixed (e.g. by adding code to free that
Tim> memory).  Admittedly, for non-pointer semantic values, this means
Tim> that you do indeed have to write the bison equivalent of a (void)
Tim> in the grammar.

I have some ideas (stolen from Lemon) about this: there is no reason
not to yydestruct the $n which are not mentioned in the code.  But
this is a longer term issue, yydestruct is not even activated.