Re: Error in GLR parser

[address@hidden]

Hello,
  first thanks for your answer.
The parsing algorithm works fine, however, I was not able to find a safe  
way how to
access "yytext" or another global variable in semantic
actions that represents the terminal's attribute (the current yytext  
corresponding to a terminal).

I was also searching on the net, but I could not find anything that seemed  
reliable.
Maybe to create my own stack of attributes?

Is there some standard way of assigning attributes to terminals for GLR  
parser?
Or could you redirect me, where could I ask, I know that this mailing list  
is intended
mainly for bugs.

Thank you
  Adam

At 16.03.2010, 16:18, wrote Joel E. Denny <address@hidden>:

> On Tue, 16 Mar 2010, ihusar wrote:
>
> > The problem, at kleast what seems to me strange, is here:
>
> > Stack 0 Entering state 13  <<-------------------------------------we  
> > are in
> > state 13
> > Next token is token T_DEC_CONST ()
> > Splitting off stack 1 from 0.
> > Reduced stack 1 by rule #131; action deferred.  Now in state 56.
> > <-----------  here we get to states 56 and 54
> > Stack 1 Entering state 56
> > Next token is token T_DEC_CONST ()
> > Reduced stack 0 by rule #120; action deferred.  Now in state 54.
> > <-----------
> >
> >
> > However, there is no transition from state 13 to state 56 or 54:
>
> >  120 ynt_aut_opc_badr2AR_C_0_439__0: YT_0_ .
> >  131 ynt_aut_opc_dadr2AR_ACC_0_409__0: YT_0_ .
>
> One of these reductions is being performed, so state 13 is popped from  
> the
> stack before the transition to state 56 or state 54.