.
cl-loop-parser.y
Description: Binary data
On Nov 9, 2008, at 3:08 PM, Joel E. Denny wrote:
On Sun, 9 Nov 2008, Nelson Ferreira wrote:
I have a very very simple parser and in 2.3 I could define some
additional
functions using YYSTYPE just by including the generated header
because it
I have a very very simple parser and in 2.3 I could define some
additional functions using YYSTYPE just by including the generated
header because it defined:
#if ! defined YYSTYPE && ! defined YYSTYPE_IS_DECLARED
typedef int YYSTYPE;
# define yystype YYSTYPE /* obsolescent; will be withdrawn
Or maybe bison should give an error when %token is used without
a %union ?
On Nov 9, 2008, at 3:59 PM, Nelson Ferreira wrote:
On Nov 9, 2008, at 3:45 PM, Joel E. Denny wrote:
On Sun, 9 Nov 2008, Nelson Ferreira wrote:
Attached is the .y file.
This is a part of the SXEmacs source
On Nov 9, 2008, at 3:45 PM, Joel E. Denny wrote:
On Sun, 9 Nov 2008, Nelson Ferreira wrote:
Attached is the .y file.
This is a part of the SXEmacs source, where we had a report of a
build failure
with bison 2.4 which we tracked down to this behavior.
The relevant files would be under
