Jeannot Langlois wrote:
In a reentrant GLR parser, how must the yyparse() caller proceed to
access the filled AST after a successful parse? I was expecting
yyparse() to return a pointer (whose type could be custom-defined by
the user just like the yylex() and yyparse() input parameter
At 12:11 -0400 2005/05/08, Jeannot Langlois wrote:
I am not sure the %glr parser currently works in pure mode. Let's cc
Paul Hilfinger, who wrote it, to see if he can let us know.
-- Hans Aberg Hi Hans (and Hi all), Just a few minutes after I
posted the question to the mailing list, I found what
In a reentrant GLR parser, how must the yyparse() caller proceed to
>access the filled AST after a successful parse? I was expecting
>yyparse() to return a pointer (whose type could be custom-defined by
>the user just like the yylex() and yyparse() input parameters) to
>the properly-fil
At 17:47 -0400 2005/05/07, Jeannot Langlois wrote:
In a reentrant GLR parser, how must the yyparse() caller proceed to
access the filled AST after a successful parse? I was expecting
yyparse() to return a pointer (whose type could be custom-defined by
the user just like the yylex() and yyparse(
Hi all,
In a reentrant GLR parser, how must the yyparse() caller proceed to
access the filled AST after a successful parse? I was expecting
yyparse() to return a pointer (whose type could be custom-defined by
the user just like the yylex() and yyparse() input parameters) to the
properly-fille
