--- On Tue, 11/4/08, Akim Demaille <[EMAIL PROTECTED]> wrote:

> From: Akim Demaille <[EMAIL PROTECTED]>
> Subject: Re: bison 2.4 breaks libIDL 0.8.11 build
> Cc: "Juergen Daubert" <[EMAIL PROTECTED]>, bug-bison@gnu.org
> Date: Tuesday, November 4, 2008, 11:40 AM
> Le 4 nov. 08 à 15:45, Sergei Steshenko a écrit :
> > You have probably also read
> > 
> >
> http://lists.gnu.org/archive/html/bug-bison/2008-11/msg00001.html
> > 
> > thread.
> > 
> > Since too many things are broken by bison 2.4 I
> suggest to
> > recall/remove/blacklist this release. I.e. the release
> doesn't feel
> > production-worthy.
> Dear Sergei,
> This is a bit harsh.  WRT the ; issue, AFAIR POSIX requires
> that the user provides a complete command.  So GCC's
> treelang should be fixed.  I am trying to build it so that I
> can send them the patch. Bison 2.4.1 will make special
> adjustments so that Treelang 4.3.2 builds properly, but
> hopefully when Bison 2.5 is out, the GCC team will have make
> releases with a fixed grammar and the workaround will no
> longer be needed.

Probably this is harsh.

But look at this from end user's point of view - something used to work
and now it doesn't.

I think that monumental projects like 'bison' should have a regression
suite which includes major users of their code.

By the way, I'm building 'gcc' using my AppsFromScratch, and I'm also
building 'libIDL' in the same framework. I didn't try to build 'libIDL'
because 'gcc' failure was enough of show stopper for me, otherwise I would
have uncovered the 'libIDL' issue too.

AppsFromScratch happens to be a really good regression testing tool,
look, for example, at another recently reported regression issue:


So, if you are interested,l I can send you a snapshot and explain how to
use it. I myself depend on the tool, so I have personal interest in
maintaining it.

My point is that even if 'gcc', 'libIDL', etc developers write erroneous
grammars, new 'bison' releases should be accompanied by release notes
notifying "big" users of problems uncovered in their code.


Reply via email to