Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-09 12:23:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

* configure.in (AC_INIT): Bump to 1.49b.

Browse Source 
(AM_INIT_AUTOMAKE): Short invocation.
This commit is contained in:
Akim Demaille
2002-05-02 09:25:54 +00:00
parent b85481146a
commit 6cbfbcc58c
6 changed files with 14 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@@ -1,3 +1,8 @@
2002-05-02 Akim Demaille <akim@epita.fr>
* configure.in (AC_INIT): Bump to 1.49b.
(AM_INIT_AUTOMAKE): Short invocation.
2002-05-02 Akim Demaille <akim@epita.fr> 2002-05-02 Akim Demaille <akim@epita.fr>
Version 1.49a. Version 1.49a.

2
NEWS
View File

@@ -1,7 +1,7 @@
Bison News Bison News
---------- ----------
Changes in version 1.49a: Changes in version 1.49b:
* Undefined token * Undefined token
The undefined token was systematically mapped to 2 which prevented The undefined token was systematically mapped to 2 which prevented

48
TODO
View File

@@ -1,49 +1,11 @@
-*- outline -*- -*- outline -*-
* URGENT: Prologue * Several %unions
The %union is declared after the user C declarations. It can be I think this is a pleasant (but useless currently) feature, but in the
a problem if YYSTYPE is declared after the user part. future, I want a means to %include other bits of grammars, and _then_
it will be important for the various bits to define their needs in
Actually, the real problem seems that the %union ought to be output %union.
where it was defined. For instance, in gettext/intl/plural.y, we
have:
%{
...
#include "gettextP.h"
...
%}
%union {
unsigned long int num;
enum operator op;
struct expression *exp;
}
%{
...
static int yylex PARAMS ((YYSTYPE *lval, const char **pexp));
...
%}
Where the first part defines struct expression, the second uses it to
define YYSTYPE, and the last uses YYSTYPE. Only this order is valid.
Note that we have the same problem with GCC.
I suggest splitting the prologue into pre-prologue and post-prologue.
The reason is that:
1. we keep language independance as it is the skeleton that joins the
two prologues (there is no need for the engine to encode union yystype
and to output it inside the prologue, which breaks the language
independance of the generator)
2. that makes it possible to have several %union in input. I think
this is a pleasant (but useless currently) feature, but in the future,
I want a means to %include other bits of grammars, and _then_ it will
be important for the various bits to define their needs in %union.
When implementing multiple-%union support, bare the following in mind: When implementing multiple-%union support, bare the following in mind:

2
config/prev-version.txt
View File

@@ -1 +1 @@
1.29c 1.49a

4
configure.in
View File

@@ -20,10 +20,10 @@
# We need a recent Autoconf to run a recent Autotest. # We need a recent Autoconf to run a recent Autotest.
AC_PREREQ(2.53) AC_PREREQ(2.53)
AC_INIT([GNU Bison], [1.49a], [bug-bison@gnu.org]) AC_INIT([GNU Bison], [1.49b], [bug-bison@gnu.org])
AC_CONFIG_AUX_DIR(config) AC_CONFIG_AUX_DIR(config)
AM_INIT_AUTOMAKE([bison], [1.49a]) AM_INIT_AUTOMAKE
AM_CONFIG_HEADER(config.h:config.hin) AM_CONFIG_HEADER(config.h:config.hin)
# Initialize the test suite. # Initialize the test suite.

1
po/sv.po
View File

@@ -1,7 +1,6 @@
# Swedish messages for bison. # Swedish messages for bison.
# Copyright © 2001, 2002 Free Software Foundation, Inc. # Copyright © 2001, 2002 Free Software Foundation, Inc.
# Göran Uddeborg <goeran@uddeborg.pp.se>, 2001, 2002. # Göran Uddeborg <goeran@uddeborg.pp.se>, 2001, 2002.
# $Revision$
# #
msgid "" msgid ""
msgstr "" msgstr ""