[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Another - Bison 1.35 works but Bison 1.50 Doesn't
From: |
Akim Demaille |
Subject: |
Re: Another - Bison 1.35 works but Bison 1.50 Doesn't |
Date: |
14 Oct 2002 10:32:43 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) |
>>>>> "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.
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Paul Eggert, 2002/10/12
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Akim Demaille, 2002/10/13
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Paul Eggert, 2002/10/13
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Akim Demaille, 2002/10/13
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Paul Eggert, 2002/10/14
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Tim Van Holder, 2002/10/14
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Paul Eggert, 2002/10/14
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Tim Van Holder, 2002/10/14
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't,
Akim Demaille <=
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Akim Demaille, 2002/10/14
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Akim Demaille, 2002/10/14
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Paul Eggert, 2002/10/14
- Re: Another - Bison 1.35 works but Bison 1.50 Doesn't, Akim Demaille, 2002/10/14