[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with multiple parsers
From: |
Akim Demaille |
Subject: |
Re: Problem with multiple parsers |
Date: |
Thu, 29 Jan 2015 21:15:30 +0100 |
> Le 29 janv. 2015 à 10:32, Laurence Finston <address@hidden> a écrit :
>
> Hello,
>
>> What version of Bison are you using?
>
> 2.6.5 and 3.0.2. I plan on installing 3.0.4 before too long.
3.0.2 is close enough :)
>> prefix I guess.
>
> No, I actually meant a suffix, e.g., MESSAGE_YY, MESSAGE_ZZ, MESSAGE_XX for
> tokens in three different parsers. I was assuming that the tokens were
> defined as preprocessor macros. I think this was once the case, but I'm not
> completely sure.
Yes it was, but it also depends on the skeleton you
use.
> At any rate, I've now checked and found that they are not now.
Well, indeed, it's probably not needed, and if you really
want something like that, I would recommend checking
api.token.prefix.
http://www.gnu.org/software/bison/manual/html_node/_0025define-Summary.html
- Problem with multiple parsers, Laurence Finston, 2015/01/28
- Re: Problem with multiple parsers, Akim Demaille, 2015/01/29
- Re: Problem with multiple parsers, Laurence Finston, 2015/01/29
- Re: Problem with multiple parsers,
Akim Demaille <=
- Re: Problem with multiple parsers, Laurence Finston, 2015/01/30
- Re: Problem with multiple parsers, Akim Demaille, 2015/01/30
- Re: Problem with multiple parsers, Laurence Finston, 2015/01/30
- Re: Problem with multiple parsers, Akim Demaille, 2015/01/30
- Re: Problem with multiple parsers, Laurence Finston, 2015/01/30
- Re: Problem with multiple parsers, Akim Demaille, 2015/01/30