It probably is a bug. I for one use bison/yacc very sparingly only and
lack the experience how to deal with it portably. Which is why it would
be better if someone else worked on fixing it.
For whatever it's worth, I have always found bison's C++ support to be
sub-par. It's always been easier
Ralf Wildenhues wrote:
> It probably is a bug. I for one use bison/yacc very sparingly only and
> lack the experience how to deal with it portably. Which is why it would
> be better if someone else worked on fixing it.
For whatever it's worth, I have always found bison's C++ support to be
sub-p
Hello Brad,
* Brad Larsen wrote on Tue, Feb 26, 2008 at 06:11:59AM CET:
>
> I'm also using autotools for a project. I'm also using bison's ability
> to output C++ parsers rather than plain C parsers. When operating in
> this mode, bison generates a few more files: stack.hh, location.hh, and
I searched for this and found no solutions, so here goes.
I'm also using autotools for a project. I'm also using bison's ability to
output C++ parsers rather than plain C parsers. When operating in this
mode, bison generates a few more files: stack.hh, location.hh, and
position.hh. The y
