[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: assert failure at line 1896
From: |
Paul Eggert |
Subject: |
Re: assert failure at line 1896 |
Date: |
Mon, 29 May 2006 21:44:26 -0700 |
User-agent: |
Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
"Joel E. Denny" <address@hidden> writes:
> Searching for `#define' in the Open Group's yacc spec, I see no
> discussion of the yacc user ever specifying a #define.
You missed YYDEBUG. Other than that, Posix doesn't say what happens
if the user #defines a macro beginning with YY -- the behavior is
undefined in that case, which is why Bison can depend on those
user-defined macros.
> So, macros should be only a Bison backward-compatibility issue, right?
If by that you mean "macros defined by the user whose names begin
with yy or YY", then I would demur for the following macros:
YYDEBUG
YYMAXDEPTH
YYSTYPE
since Solaris 10 yacc generates a parser whose behavior also depend on
these user-defined macros, in a way that's compatible with Bison.
(For what it's worth, the Solaris 10 parser also depends on YYEXPAND,
YYNMBCHARS, yyerror, and yylex.)
- Re: assert failure at line 1896, (continued)
Re: assert failure at line 1896, Akim Demaille, 2006/05/29
Re: assert failure at line 1896,
Paul Eggert <=
Re: assert failure at line 1896, Joel E. Denny, 2006/05/30
Re: assert failure at line 1896, Paul Eggert, 2006/05/21