Dear Bison-users,
I'm working on a prototype of a COBOL-parser in bison using a GLR-parser.
I have a question considering YYABORT:
When the parsing-process uses more then one parser, and one of them encounters
this macro, will only this parser stop, or all of them. And if the second is
the case
[Please try to give descriptive subjects; replies should cc the Help-
Bison list.]
On 12 Dec 2006, at 12:28, [EMAIL PROTECTED] wrote:
I'm working on a prototype of a COBOL-parser in bison using a GLR-
parser.
I have a question considering YYABORT:
When the parsing-process uses more then one p
On Tue, 12 Dec 2006, Hans Aberg wrote:
> [Please try to give descriptive subjects; replies should cc the Help-Bison
> list.]
>
> On 12 Dec 2006, at 12:28, [EMAIL PROTECTED] wrote:
>
> > I'm working on a prototype of a COBOL-parser in bison using a GLR-parser.
> > I have a question considering YY
On 12 Dec 2006, at 20:39, Joel E. Denny wrote:
I'm working on a prototype of a COBOL-parser in bison using a GLR-
parser.
I have a question considering YYABORT:
When the parsing-process uses more then one parser, and one of them
encounters this macro, will only this parser stop, or all of
the
On 12 Dec 2006, at 20:39, Joel E. Denny wrote:
Maybe there's a confusion in terminology here:
YYABORT stops the single GLR parser (that is, yyparse).
In the case of GLR, would it not be best to call yyparse the parser,
and the splits branches of this single parser. This will avoid the
con
Hello
i want to write a parser with bison using some containers from STL but i
don't need an oriented objet parser : yyparse() is sufficient for me !
Have i to use skeleton and all the C++ stuff of bison manual ?
--
Cordialement, Michel Meynard.
Michel
No, you dont need to use the C++ skeleton. Just put an extern "C"
declaration at the beggining of your parser file (.y file) e.g.,
extern "C"
{
int yyparse ( void );
int yylex ( void );
int yywrap ();
void yyerror ( char* );
}
satya.
--
Work expands to fill the time available for
On 13 Dec 2006, at 00:09, Satya wrote:
No, you dont need to use the C++ skeleton. Just put an extern "C"
declaration at the beggining of your parser file (.y file) e.g.,
extern "C"
{
int yyparse ( void );
int yylex ( void );
int yywrap ();
void yyerror ( char* );
}
Putting the
Putting the in the .y file would not suffice, as those functions need
to be put in a file compiled by the C++ associated C-compiler;
Well, when Bison generates an xyz.tab. c file, it can be compiled by a C++
compiler. Thats the idea.
one
cannot then use C++ containers. If the C-parser is comp
On 13 Dec 2006, at 01:11, Satya wrote:
Putting the in the .y file would not suffice, as those functions need
to be put in a file compiled by the C++ associated C-compiler;
Well, when Bison generates an xyz.tab. c file, it can be compiled
by a C++ compiler. Thats the idea.
Once upon the time
10 matches
Mail list logo
