|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:||Bill Cox <firstname.lastname@example.org>|
|Date:||8 Nov 2005 23:34:53 -0500|
|Posted-Date:||08 Nov 2005 23:34:53 EST|
Andrey Tarasevich 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]
Return to the
Search the comp.compilers archives again.