bison-2.6.3 released [stable]

[Akim Demaille]

The Bison team is happy to announce the release on Bison 2.6.3, a
bug-fix release.

Here are the compressed sources:
ftp://ftp.gnu.org/gnu/bison/bison-2.6.3.tar.gz (3.1MB)
ftp://ftp.gnu.org/gnu/bison/bison-2.6.3.tar.xz (1.7MB)

Here are the GPG detached signatures[*]:
ftp://ftp.gnu.org/gnu/bison/bison-2.6.3.tar.gz.sig
ftp://ftp.gnu.org/gnu/bison/bison-2.6.3.tar.xz.sig

Use a mirror for higher download bandwidth:
http://www.gnu.org/order/ftp.html

[*] Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:

gpg --verify bison-2.6.3.tar.gz.sig

If that command fails because you don't have the required public key,
then run this command to import it:

gpg --keyserver keys.gnupg.net --recv-keys 0DDCAA3278D5264E

and rerun the 'gpg --verify' command.

This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.12.4
Flex 2.5.37
Gettext 0.18.1
Gnulib v0.0-7675-gd245e6d

NEWS

* Noteworthy changes in release 2.6.3 (2012-10-22) [stable]

** Bug fixes

Bugs and portability issues in the test suite have been fixed.

Some errors in translations have been addressed, and --help now directs
users to the appropriate place to report them.

Stray Info files shipped by accident are removed.

Incorrect definitions of YY_, issued by yacc.c when no parser header is
generated, are removed.

All the generated headers are self-contained.

** Header guards (yacc.c, glr.c, glr.cc)

In order to avoid collisions, the header guards are now
YY_<PREFIX>_<FILE>_INCLUDED, instead of merely <PREFIX>_<FILE>.
For instance the header generated from

%define api.prefix "calc"
%defines "lib/parse.h"

will use YY_CALC_LIB_PARSE_H_INCLUDED as guard.

** Fix compiler warnings in the generated parser (yacc.c, glr.c)

The compilation of pure parsers (%define api.pure) can trigger GCC
warnings such as:

input.c: In function 'yyparse':
input.c:1503:12: warning: 'yylval' may be used uninitialized in this
function [-Wmaybe-uninitialized]
*++yyvsp = yylval;
^

This is now fixed; pragmas to avoid these warnings are no longer needed.

Warnings from clang ("equality comparison with extraneous parentheses" and
"function declared 'noreturn' should not return") have also been
addressed.