bison-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: too many warnings from Bison CVS for Pike


From: Hans Aberg
Subject: Re: too many warnings from Bison CVS for Pike
Date: Mon, 30 Jan 2006 01:44:32 +0100

On 29 Jan 2006, at 23:49, Joel E. Denny wrote:

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.

The problem is that we do not know what this interpretation ought to be. If one does not want to break old code, then one can stick with what has been in the past.

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.

The compile C as C++ option was never official, therefore no notice was made, I gather. But it was a few years ago. The point is that the $$ = $1 seems to fall into the same category: not explicitly official, but used by some because it works.

  Hans Aberg






reply via email to

[Prev in Thread] Current Thread [Next in Thread]