On Tue, Nov 2, 2010 at 18:34, Philip Herron wrote:
> To be honest i think its more of a problem of the code bison is
> generating, though i should look into what happens in GLR parser and
> C++ i want to see for myself to judge it. But i do feel its on the
> bison side of things it shouldnt assume
To be honest i think its more of a problem of the code bison is
generating, though i should look into what happens in GLR parser and
C++ i want to see for myself to judge it. But i do feel its on the
bison side of things it shouldnt assume the name of the header and
auto include. I assume though th
Philip Herron writes:
> Yeah this all seems like a bug to me, i dont do much C++ i prefer to
> use C so i havent used C++ bison parsers et'al . But yeah i have a few
> work arounds to get multiple bison and flex working i have some work i
> want to do to ylwrap to help it all but i really haven't
