bison-2.1

[markh@…]

new version out

[markh@…]

new version (1.30). why didn't we go to 1.29 - there was a reason. try and find out and see if it's fixed before upgrading

[markh@…]

bison-1.31 released.

The problem with 1.29 was to do with compiling X, see:

​http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2001/09/1370.html

I can't confirm it's been fixed now because I don't recall being able to reproduce it in the first place. Suggest we go to 1.31 and then make sure we do the usual tests (such as building X etc) before the next point release; then we can downgrade if necessary. Marc, Gerard, is that OK?

[gerard@…]

Sure sounds good

[markh@…]

updated to bison-1.31

[gimli@…]

Bison 1.32 is released >:(

[gerard@…]

This update can wait until after lfs-3.2

[gimli@…]

And another Bison release :) This one should fix the groff + gcc 3.x troubles.

[gerard@…]

updated in book

[markh@…]

checked that 1.38 installs ok. closing

[markh@…]

that should have course read "1.34" not "1.38"

[markh@…]

bison-1.35 out

[highos@…]

Version increment (1.50);

• configure.ac (AC_INIT), NEWS: Increment version number.

• doc/bison.texinfo: Minor spelling, grammar, and white space fixes. (Symbols): Mention that any negative value returned from yylex signifies end-of-input. Warn about negative chars. Mention the portable Standard C character set.

The GNU coding standard says CFLAGS and YFLAGS are reserved for the installer to set.

• lib/Makefile.am (AM_CFLAGS): Renamed from CFLAGS.
• src/Makefile.am (AM_CFLAGS): Likewise. (AM_YFLAGS): Renamed from YFLAGS.

Fix some MAX and MIN problems.

• src/gram.h (ITEM_NUMBER_MIN): MIN_MAX -> INT_MIN.
• src/lalr.h (GOTO_NUMBER_MAX): INT_MAX -> SHRT_MAX.
• src/symtab.h (SYMBOL_NUMBER_MAX): New macro.
• src/reader.c (reader): Use it.

• tests/regression.at (Braces parsing): Use grep, not fgrep, as POSIX 1003.1-2001 has removed fgrep.

[highos@…]

Version increment (1.75);

• Bison should now work on 64-bit hosts.

• Indonesian translation thanks to Tedi Heriyanto.

• GLR parsers Fix spurious parse errors.

• Pure parsers Some people redefine yyerror to steal yyparse' private variables. Reenable this trick until an official feature replaces it.

• Type Clashes In agreement with POSIX and with other Yaccs, leaving a default action is valid when $$ is untyped, and $1 typed:

untyped: ... typed;

but the converse remains an error:

typed: ... untyped;

• Values of mid-rule actions The following code:

foo: { ... } { $$ = $1; } ...

was incorrectly rejected: $1 is defined in the second mid-rule action, and is equal to the $$ of the first mid-rule action.

[timothy@…]

Version Increment (1.875)

[Matthew Burgess]

See ​http://lists.gnu.org/archive/html/bug-bison/2004-12/msg00080.html. It's only on alpha.gnu.org at the moment, but should be on ftp.gnu.org shortly.

[jeremy@…]

Upgraded to 2.0 in unstable.

[Matthew Burgess]

Version increment (2.1)