Re: too many warnings from Bison CVS for Pike

[Joel E. Denny]

On Sun, 29 Jan 2006, Hans Aberg wrote:

> On 29 Jan 2006, at 21:56, Joel E. Denny wrote:
> 
> > On Sun, 29 Jan 2006, Hans Aberg wrote:
> > 
> > > On 29 Jan 2006, at 20:11, Joel E. Denny wrote:
> > > 
> > > > >   %define pre-switch { if (yylen >= 1)  $$ = $1; }
> > > > 
> > > > This isn't yacc compatible.
> > > 
> > > That depends on the interpretation of the Yacc specification.
> > 
> > ???
> 
> ???

:) I was seeking more information on this alternate interpretation, but 
maybe it's more useful if I just revise my wording: s/compatible/portable/

> > Which doesn't give any `explicit directions' for the value for the rule.
> 
> Sure it does: Do not do anything. This is useful under C++, if one wants to
> avoid unneeded copying.
> 
> > > Should then $$ = $1 be applied?
> > 
> > Under yacc, I'm saying yes.
> 
> But it is not a question of what you think, but what the POSIX spec intends.

Yes, I was trying to tell you what I think the POSIX spec intends. :)

In any case, as I said before, this debate of what they meant could last a 
while.  So, I suggested the short cut of just choosing what bison should 
do for --yacc based on a portable interpretation of the spec.

> One example is the unofficial
> compile C as C++ that existed for awhile, but that was abandoned in view that
> it was too difficult to maintain.

This is way off topic, but when was this abandoned?  make maintainer-check 
would need to be updated.

Joel