Re: confusing bison error

2020-11-28 Thread Akim Demaille
Hi Jot, > Le 27 nov. 2020 à 11:20, Jot Dot a écrit : > >> What do you mean? It did display "go to state 31", but did not? Could you >> please provide us with the full trace? Also, have you tried to enable the >> Flex traces, just in case. > > My input string is "CONST\n\trange = 1..10;\n" >

Re: confusing bison error

2020-11-28 Thread John P. Hartmann
His goof was to specify '=' (three characters) in flex. So the = token never got to the parser. On 11/28/20 09:49, Akim Demaille wrote: Hi Jot, Le 27 nov. 2020 à 11:20, Jot Dot a écrit : What do you mean? It did display "go to state 31", but did not? Could you please provide us with the

Re: confusing bison error

2020-11-28 Thread Akim Demaille
Hi John, > Le 28 nov. 2020 à 11:27, John P. Hartmann a écrit : > > His goof was to specify '=' (three characters) in flex. So the = token never > got to the parser. Doh... I didn't see it :( Thanks for the resolution of the mystery :)