misleading diagnostics in Bison-generated parser trace

In Joel E. Denny writes: > I also noticed this at the end of the parser trace: > Error: popping token $end ()Error: popping nterm tree ()Error: popping > token $end () > This did not happen with prior versions of bison for

Re: redundant merges for GLR

On Sun, 21 Aug 2005, Paul Eggert wrote: > bug-bison would have been better I'll do that next time. > I'm a bit worried about the storage management for the deleted nodes > (did you look into that?) Yes. I believe all SemanticOption's are pulled from nextFree of a GLRStack. That is, they come

Re: redundant merges for GLR

"Joel E. Denny" <[EMAIL PROTECTED]> writes: >> I haven't seen any response to my posts last month on problems I'm having >> with bison GLR: >> >> http://lists.gnu.org/archive/html/help-bison/2005-07/msg00013.html >> http://lists.gnu.org/archive/html/help-bison/2005-07/msg00040.html >> http:/

print reduced input string

Hello How is it possible to print out the input value reduced by a rule inside an action . As an example: stmts:stmts, stmt | stmt { printf(???); } For example stmt is an "if a then b" statement. The $1 value of this stmt returns me a "if" node. I do

Re: redundant merges for GLR

On Wed, 10 Aug 2005, Joel E. Denny wrote: > On Fri, 29 Jul 2005, Joel E. Denny wrote: > > > On Tue, 19 Jul 2005, Joel E. Denny wrote: > > > > > I am attempting to use bison's %glr-parser and %merge to construct parse > > > forests. I'm getting duplicate representations of some trees within the >