this patch made my parser and lexer compile. thanks. unfortunately, three
things
make it hard for me to investigate further at the moment.
1. in the meantime, i've had hand surgery, and my typing is inaccurate and
laborious.
the pain meds don't help, either.
2. i'm working from a batch-m
On Tue, 12 Aug 2008, Lucian Smith wrote:
> If I recall correctly, in my own C++ code, I had to have an actual
> grammar line that *used* 'yyerrok' before bison would put the relevant
> code into the .tab.cpp file.
> Similar things happened with yylloc, I believe.
Bison parses semantic actions
If I recall correctly, in my own C++ code, I had to have an actual
grammar line that *used* 'yyerrok' before bison would put the relevant
code into the .tab.cpp file. If I didn't, it would never put it in,
and other code that tried to reference it would run into problems.
Something like:
inpu
On Tue, 12 Aug 2008, Laurence Finston wrote:
> On Mon, 11 Aug 2008, kogorman wrote:
>
> > Nope, I grep for yyerrok on all files in the directory, and see only my own
> > code and
> > things directly generated from it. I do not see a #define or other
> > definiton.
Thanks for the report.
There
On Mon, 11 Aug 2008, kogorman wrote:
> Laurence Finston wrote:
>
> Nope, I grep for yyerrok on all files in the directory, and see only my own
> code and
> things directly generated from it. I do not see a #define or other
> definiton.
> Did you do this from the code I included, or some of you
Laurence Finston wrote:
>
> On Mon, 11 Aug 2008, kogorman wrote:
>
>>
>> All this is true, but beside the point. What's missing is yyerrok, not
>> yyerror.
>
> This is what you wrote:
>
>> >> But my C++ parser
>> >> won't compile because (it says) yyerror was not declared in this
>> context
On Mon, 11 Aug 2008, kogorman wrote:
>
> All this is true, but beside the point. What's missing is yyerrok, not
> yyerror.
This is what you wrote:
> >> But my C++ parser
> >> won't compile because (it says) yyerror was not declared in this context.
> I've got the required yyerror and yylex.
All this is true, but beside the point. What's missing is yyerrok, not
yyerror.
I've got the required yyerror and yylex.
I'm using a C++ setup because I don't want to mix FILE* and C++ streams,
and just because it seems the Right Thing To Do (TM).
++ kevin
Laurence Finston wrote:
>
>> The
> The C examples show using yyerror and the examples compile and run okay.
> But my C++ parser
> won't compile because (it says) yyerror was not declared in this context.
> And when I look at
> the generated code, the #define I see in the C scanners is missing. This is
> a nuisance; is there
>
I'm developing a very simple parser to frontend to an existing C++ board game
(named "six").
I'm following the examples as best I can, but my attempts at syntax error
handling are failing.
The C examples show using yyerror and the examples compile and run okay.
But my C++ parser
won't compile b
10 matches
Mail list logo
