Re: Problem with multiple parsers

2015-01-30 Thread Akim Demaille
> Le 30 janv. 2015 à 15:40, Laurence Finston a écrit : > > Hello, > >> My current project is for my work and I'm not allowed to publish any code. >> However, I used three scanner/parser pairs in a >> recent project for my previous job and it can be downloaded from Github: >> https://github

Re: Problem with multiple parsers

2015-01-30 Thread Laurence Finston
the gwrdifpk/doc, however, in case anyone is interested. Laurence > Gesendet: Freitag, 30. Januar 2015 um 15:21 Uhr > Von: "Laurence Finston" > An: "Akim Demaille" > Cc: "Bison Bugs" > Betreff: Re: Problem with multiple parsers > > Hello

Re: Problem with multiple parsers

2015-01-30 Thread Akim Demaille
> Le 30 janv. 2015 à 15:21, Laurence Finston a écrit : > > Hello, > >> yes, that would be nice. Or if you have a tarball we could >> have a look at. > > My current project is for my work and I'm not allowed to publish any code. > However, I used three scanner/parser pairs in a recent projec

Re: Problem with multiple parsers

2015-01-30 Thread Laurence Finston
nd flex work together. The solution I found with %name-prefix is definitely not ideal, but I haven't been able to get it to work with `%define api.prefix' at all yet. Laurence > Gesendet: Freitag, 30. Januar 2015 um 14:40 Uhr > Von: "Akim Demaille" > An: "La

Re: Problem with multiple parsers

2015-01-30 Thread Akim Demaille
> Le 30 janv. 2015 à 11:30, Laurence Finston a écrit : > > Hello, Hi Laurence, > I tried defining YY_DECL as you suggested, but I still couldn't get it to > work. The program is already fairly complex so it's not easy to test just > the problem of getting multiple parsers to work together.

Re: Problem with multiple parsers

2015-01-30 Thread Laurence Finston
ng to a new version of Bison would break my code. I dont know how many other people would be affected by this. Thanks, Laurence > Gesendet: Donnerstag, 29. Januar 2015 um 21:15 Uhr > Von: "Akim Demaille" > An: "Laurence Finston" > Cc: "Bison Bu

Re: Problem with multiple parsers

2015-01-29 Thread Akim Demaille
> Le 29 janv. 2015 à 10:32, Laurence Finston 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_

Re: Problem with multiple parsers

2015-01-29 Thread Laurence Finston
don't trust Flex's > Bison bridge. Okay, I'll try this. It sounds like it should work. Thanks, Laurence > Gesendet: Donnerstag, 29. Januar 2015 um 09:44 Uhr > Von: "Akim Demaille" > An: "Laurence Finston" > Cc: "Bison Bugs"

Re: Problem with multiple parsers

2015-01-29 Thread Akim Demaille
> Le 28 janv. 2015 à 14:59, Laurence Finston a écrit : > > Hello, Hi! What version of Bison are you using? > I've used multiple parsers in a few projects using the `%name-prefix' option. > Some other files included more than one of the generated header files which > meant that the %union t

Problem with multiple parsers

2015-01-28 Thread Laurence Finston
Hello, I've used multiple parsers in a few projects using the `%name-prefix' option. Some other files included more than one of the generated header files which meant that the %union type had to be the same for all the parsers. However, in practice, this wasn't a problem. In addition, I use