[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Re: named references
From: |
Joel E. Denny |
Subject: |
Re: [PATCH] Re: named references |
Date: |
Fri, 20 Mar 2009 17:07:58 -0400 (EDT) |
On Fri, 20 Mar 2009, Akim Demaille wrote:
>
> Le 20 mars 09 ? 16:23, Joel E. Denny a ?crit :
>
> > > I'm not sure asymmetric will be understandable in error messages.
> > > Maybe "partial" would be more appropriate?
> >
> > I agree "asymmetric" is a confusing name. "partial" may be better. A few
> > other ideas off the top of my head: "incomplete", "nonuniform",
> > "inconsistent".
>
> Or reword completely:
>
> incomplete resolution of name collision on `foo'
A simpler possibility may be to just say "reference is misleading" as in
the case where dots cause confusion. A "refers to" and "possibly meant"
will clear up the confusion. For example:
lhs: rhs[first] rhs { $rhs; } ;
Bison would report:
interpreter.ypp:74.43-52: reference is misleading: `$rhs'
interpreter.ypp:73.38-46: (refers to: `$[rhs]' at $2)
interpreter.ypp:73.38-46: (possibly meant: `$[rhs]' hidden at $1)
(I didn't update column numbers, so ignore that.)
- named references, Alex Rozenman, 2009/03/06
- Re: named references, Joel E. Denny, 2009/03/08
- Re: [PATCH] Re: named references, Joel E. Denny, 2009/03/20
- Re: [PATCH] Re: named references, Akim Demaille, 2009/03/20
- Re: [PATCH] Re: named references,
Joel E. Denny <=
- Re: [PATCH] Re: named references, Joel E. Denny, 2009/03/20
- Re: [PATCH] Re: named references, Alex Rozenman, 2009/03/22
- Re: [PATCH] Re: named references, Joel E. Denny, 2009/03/20
- Re: [PATCH] Re: named references, Akim Demaille, 2009/03/20
- Re: [PATCH] Re: named references, Joel E. Denny, 2009/03/20
- Re: [PATCH] Re: named references, Alex Rozenman, 2009/03/22