[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
User Token Numbers
From: |
Akim Demaille |
Subject: |
User Token Numbers |
Date: |
08 Apr 2002 19:20:17 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) |
While writing test cases I fell on some weird behaviors: 1.28 (I don't
know for 1.3x, I don't have it at hand, but I'd say it behaves
equally) accepts that you
%token FOO 2
although 2 is used for $undefined. Nice from it to accept, but it
would be better if the parser knew that. It does not, and FOO and
$undefined do collide at runtime.
1.5x refuses:
foo.y:32: tokens "1" and $undefined. both assigned number 2
(the message showed up as part of the various clean ups, so they _are_
useful :).
Neither is OK I guess. But I would like to know more from POSIX, in
particular, I would like to make sure that EOF (= 0) is the only
number that is reserved.
Also, but that's another matter: what does POSIX say about
reduce/reduce conflicts?
- User Token Numbers,
Akim Demaille <=
- Re: User Token Numbers, Paul Eggert, 2002/04/08
- Re: User Token Numbers, Akim Demaille, 2002/04/08
- Re: User Token Numbers, Paul Eggert, 2002/04/08
- Re: User Token Numbers, Akim Demaille, 2002/04/09
- Re: User Token Numbers, Paul Eggert, 2002/04/09
- Re: User Token Numbers, Akim Demaille, 2002/04/10
- Re: User Token Numbers, Hans Aberg, 2002/04/10
- Re: User Token Numbers, Paul Eggert, 2002/04/10
Re: User Token Numbers, Florian Krohm, 2002/04/08
Re: POSIX and reduce/reduce conflicts, Paul Eggert, 2002/04/08