Re: push parser

[Bob Rossi]

On Wed, Dec 27, 2006 at 11:38:10AM -0500, Joel E. Denny wrote:
> > > In the meantime, I think we should stay away from #1 just to avoid 
> > > conflicts.  However, feel free to work on #2, but understand that the 
> > > %push-pull-parser stuff is still evolving.  For #3, do you have any use 
> > > cases from your own work that could be converted to test cases?
> > 
> > Well, I have a grammar that implements the gdb/mi protocol. I then use
> > flex and bison to parse it. I currently don't do anything interactive
> > though, if that's what you are looking for. In fact, I don't plan on
> > ever doing anything interactive for this project. 
> 
> I'm not sure what you mean by interactive.  Would you explain a bit more?

Well, I guess I was just thinking of the nature of how I use the push
parser. I don't have all the data avaiable, so I get enough, and then
invoke the push parser.

So, I just meant that now someone can write some code that deals with a
user, and then takes the users input and parses it.

In retrospect, this probably isn't what you are interested in.

> > The reason I needed the 
> > push parser is because gdb/mi is a line oriented protocol 
> > (It emits one line at a time). If you've used gdb enough, you'll notice 
> > that sometimes when a program crashes by recursion or stack curroption,
> > if you do a backtrace in gdb it can print frames for a very long time.
> > Without the push parser, I have to wait (5-10 minutes) for the entire 
> > response to come back before passing to bison. This gives the user a 
> > bad experience. With the push parser I can alert bison after each frame
> > is printed. There are other benefits. 
> > 
> > Would the grammar be useful? or are you thinking of a contrived example
> > that is interactive?
> 
> It sounds large.  If so, can you think of a reduced example that does 
> something similar?  That would probably be easier for other developers to 
> maintain later.

Sure. You've recently made bison much more configurable in terms of a
parser. So, have you had the chance to add tests that use all the
different variations?

Should the example just use the push parser or should it switch between
push and pull mode? What exactly is the example for?

Take a look at the examples Odd originally had, what do you think of
them?

Thanks,
Bob Rossi

examples.tar.gz
Description: Binary data