|Cygwin 'byacc' question firstname.lastname@example.org (Andrey Tarasevich) (2005-11-02)|
|Re: Cygwin 'byacc' question email@example.com (Keith Thompson) (2005-11-04)|
|Re: Cygwin 'byacc' question firstname.lastname@example.org (Bill Cox) (2005-11-08)|
|Re: Cygwin 'byacc' question email@example.com (toby) (2005-11-12)|
|Re: Cygwin 'byacc' question firstname.lastname@example.org (Andrey Tarasevich) (2005-11-12)|
|Re: Cygwin 'byacc' question email@example.com (Thomas Dickey) (2005-12-19)|
|From:||Andrey Tarasevich <firstname.lastname@example.org>|
|Date:||12 Nov 2005 16:11:36 -0500|
|Organization:||Posted via Supernews, http://www.supernews.com|
|Posted-Date:||12 Nov 2005 16:11:36 EST|
Bill Cox wrote:
>> As a workaround, I can probably use a different prefix for each
>> parser, instead of the default 'yy', thus eliminating the name
>> conflict, but it is still strange to have the global namespace
>> polluted with essentially local names. Any ideas?
> The current bison version has a --name-prefix=<prefix> option,
> and it's probably not much trouble to switch from byacc to bison.
> I've switched grammars both ways in the past.
> And the latest Linux byacc that Google shows me has a very similar
> "-p <prefix>" option.
> [The -p option has been available for a very long time. -John]
I have no problem changing the prefix in byacc. But that's not the
issue. I just want to know the rationale behind that strange change in
the declaration format, if there's any. The old one made sense. The
new one doesn't. Am I missing something? Does anyone actually use
Return to the
Search the comp.compilers archives again.