Re: asynchronous MI output commands

[Daniel Jacobowitz <drow@false.org>]

On Sat, May 06, 2006 at 12:40:31PM -0400, Bob Rossi wrote:
> 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?

`OUTPUT ==>'
     `( OUT-OF-BAND-RECORD )* [ RESULT-RECORD ] "(gdb)" NL'

It's an OOB record, followed by a prompt.  It's not the direct output of
any command.

> 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?

"MI output command" doesn't mean anything to me.  It's an MI output
record, and it isn't in response to a command.

I still don't understand the question - the point of categorizing
messages in this way.

-- 
Daniel Jacobowitz
CodeSourcery