Re: asynchronous MI output commands

[Bob Rossi <bob_rossi at cox dot net>]

On Sat, May 06, 2006 at 11:20:46AM -0400, Daniel Jacobowitz wrote:
> On Sat, May 06, 2006 at 07:49:34AM -0400, Bob Rossi wrote:
> > Right, synchronous is a response to a command. That's also the
> > definition I was using. However the initial output is not a response to
> > a command and it also does not semantically end up being asynchronous.
> 
> Why do you think it is not asynchronous?  If you want to be picky about
> the grammar, it's an out of band message.

~"GNU gdb 6.1-debian\n"
~"Copyright 2004 Free Software Foundation, Inc.\n"
~"GDB is free software, covered by the GNU General Public License, and you are\n"
~"welcome to change it and/or distribute copies of it under certain conditions.\n"
~"Type \"show copying\" to see the conditions.\n"
~"There is absolutely no warranty for GDB.  Type \"show warranty\" for details.\n"
~"This GDB was configured as \"i386-linux\"..."
~"Using host libthread_db library \"/lib/libthread_db.so.1\".\n"
~"\n"
(gdb)

Each of the lines beggining with ~ are an 
  out-of-band-record => stream-record.
There is no out-of-band-record => async-record.

Certainly having an out-of-band-record => stream-record does not make an
MI output command asynchronous. Or does it?

The code I wrote to determine if an MI output command is asynchronous
checks to see if there is an out-of-band-record=>async-record in the
parse tree. If there is, the command is asynchronous, otherwise it's
not. Do you disagree with this?

Thanks,
Bob Rossi