asynchronous MI output commands

[Bob Rossi]

On Sat, May 06, 2006 at 12:05:53AM -0400, Daniel Jacobowitz wrote:
> On Fri, May 05, 2006 at 10:49:02PM -0400, Bob Rossi wrote:
> > OK, I could do this, and if that's the prefered way, then I will. The
> > only strange thing about it, is either I need to hack up the parser to
> > set a flag when it reaches that point, or I need to walk the parse tree
> > semi-deep to get that info. Do you still think that would be the
> > prefered way? Actually, I could just see if I ever get to the
> > async-record to determine if the command is asynchronous, right?
> 
> I just don't understand what your goals and terms are here.

I guess I don't either, I'm just trying to understand how to look at
each MI output command and how to classify them.

> The MI output syntax has a grammar, and the grammar has semantic
> information.  One part of the grammar identifies what is synchronous
> and what is asynchronous.  If your parser can't keep track of that
> information, then perhaps you should think a little more about what
> information you need from parsing - that's pretty much the point of
> having a parser.

I aggree with you know, just needed someone else's point of view. I'll
check the parser to see if it went down the asynchronous route. Thanks.

Bob Rossi