Re: [PATCH] Re: named references

[Akim Demaille]

>>> "AR" == Alex Rozenman <address@hidden> writes:

Hi Alex,

Thanks a lot for all this work.  I know several people who are eager
to use Bison with your contribution!

 > As you certainly know, it often happens that accurate
 > implementation changes feelings about how stuff should work.

 > Please note that "asymmetric renaming" warning is not implemented (yet).

I'm not sure asymmetric will be understandable in error messages.
Maybe "partial" would be more appropriate?

 > You may consider it "disabled" in the following examples. Actually,
 > I am not sure that it would be helpful.

I subscribe to Joel's ideas about this, I would really prefer that we
have this warning.  Actually, we didn't we make this an error?

 > /* a real ambiguity reported regardless of dots, note that dots cannot
 >     be a reason for these ambiguities */
 > if_stmt: IF expr THEN stmt.list ELSE stmt.list FI
 >            { $if_stmt = new IfStmt($expr, $stmt.list, $stmt.list); };
 > interpreter.ypp:74.43-52: reference is ambiguous: `$stmt.list'

Really, I do not like the fact that `.' be part of such ids, I'm very
much against it.  It departs completely from the usage $ in many
languages starting with shell scripts.  This is going against years of
education of our eyes, to me $stmt.list definitely means $[stmt].list.


 > if_stmt: IF expr { $<stmtptr>cond = $expr > 0; } [cond] THEN stmt[then] ELSE
 > stmt FI
 >            { $if_stmt = new IfStmt($<stmtptr>cond, $then, $stmt.list); };
 > <no errors, no warnings>

You do support $<stmtptr>[stmt.list]?