bison-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: push parser implemenation


From: Bob Rossi
Subject: Re: push parser implemenation
Date: Sun, 26 Mar 2006 09:01:33 -0500
User-agent: Mutt/1.5.9i

On Fri, Mar 24, 2006 at 10:01:16AM -0800, Paul Eggert wrote:
> "Joel E. Denny" <address@hidden> writes:
> 
> > Sorry for the silence on our part.  I think everyone must be very busy.  
> 
> Yup.  I'll have some more time next week, I think.
> 
> > On top of that, there seems to be some delay on completing 2.2,
> 
> This is more a licensing issue.  I guess we'll have to ship 2.2 with
> the old license.
> 
> (Personally I'd trust your or Akim's review over mine.  :-)

Thanks for the responds everyone. I know these things take time, I just
wanted to make sure I wasn't being swept under the rug.

I do see one problem while testing the parser after the patch. Some of
my actions are not being reached, which makes me think I've corrupted
the parser. Basically, this is the first action that is hit,
  opt_oob_record_list: {
              $$ = NULL;
  };
Any idea what could cause this? I'll do some more digging.

I've attached the bison input grammar and the test file that is
producing this behavior only after my patch is applied. Things work as
expected without my patch. I was hoping someone could glance at it
quickly and tell me if what I am seeing should be possible when bison is
working correctly.

Any tips in the right direction would probably save me hours of work. :)

Bob Rossi

Attachment: gdbmi_grammar.y
Description: Text document

Attachment: grammar_data.txt
Description: Text document

Attachment: gdbmi_lexer.l
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]