[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: default %destructor/%printer for error, $undefined, $accept
From: |
Joel E. Denny |
Subject: |
Re: FYI: default %destructor/%printer for error, $undefined, $accept |
Date: |
Mon, 21 Aug 2006 18:54:04 -0400 (EDT) |
On Mon, 21 Aug 2006, Paul Eggert wrote:
> Obviously it's bogus to copy the value from the lookahead token. But
> what about "error: ...;" rules? For them, it sort of makes sense to
> have a type for the error token.
As far as I can tell, Bison doesn't permit error token rules in any form
yet. Right?
> Perhaps if we had some way to specify the semantic value for an error
> token that is generated internally by the parser? Just thinking out
> loud here.
Can you give me an example of how error token values would be useful?
Joel
- FYI: default %destructor/%printer for error, $undefined, $accept, Joel E. Denny, 2006/08/21
- Re: FYI: default %destructor/%printer for error, $undefined, $accept, Paul Eggert, 2006/08/21
- Re: FYI: default %destructor/%printer for error, $undefined, $accept,
Joel E. Denny <=
- Re: FYI: default %destructor/%printer for error, $undefined, $accept, Paul Eggert, 2006/08/21
- Re: FYI: default %destructor/%printer for error, $undefined, $accept, Joel E. Denny, 2006/08/21
- Re: FYI: default %destructor/%printer for error, $undefined, $accept, Joel E. Denny, 2006/08/22
Re: FYI: default %destructor/%printer for error, $undefined, $accept, Joel E. Denny, 2006/08/23