[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: %destructor and unused values
From: |
John P. Hartmann |
Subject: |
Re: %destructor and unused values |
Date: |
Mon, 28 Jan 2013 17:11:23 +0100 |
Adding $$ = $1 kept Bison quiet.
Here is a variation that gets Unused value $1.
assign : variable ASSIGN expression
{
$$->term.oper = op_assign;
This is also fixed by stating the default action.
Surely this is a bug (?).
On 28 January 2013 16:43, John P. Hartmann <address@hidden> wrote:
> But here is another one:
>
> | dotobyfors dotobyfor { listend($1, $2); }
>
> Gets "warning: unset value: $$".
>
> I'm relying on the default $$ = $1 here.
>
> Or is there something more subtle going on? Or (shudder) is the
> default applied only when there is no explicit semantic code? (In
> which case I have a lot of grammars to fix.)
- %destructor and unused values, John P. Hartmann, 2013/01/28
- Re: %destructor and unused values, Akim Demaille, 2013/01/28
- Re: %destructor and unused values, John P. Hartmann, 2013/01/28
- Re: %destructor and unused values, John P. Hartmann, 2013/01/28
- Re: %destructor and unused values,
John P. Hartmann <=
- Re: %destructor and unused values, Akim Demaille, 2013/01/28
- Re: %destructor and unused values, John P. Hartmann, 2013/01/28
- Re: %destructor and unused values, Akim Demaille, 2013/01/28
- Re: %destructor and unused values, John P. Hartmann, 2013/01/28