Re: [mi] organize possible exec async mi oc command reasons

Eli Zaretskii
2005-03-27T04:42:40Z

> Date: Sat, 26 Mar 2005 22:55:29 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: gdb-patches@sources.redhat.com
>
> Thanks for all the excellent suggestions, I can see how this is much
> much nicer than what I had. There is probably still room for improving,
> what do you think?

It's fine now, I have only one minor comment, see below.

> After this doco and patch is approved, I'm going to enumerate the other
> 2 case's, status-async-output and notify-async-output.

Thanks.

> Also, For each item, I could add the MI commands that could be done to get the
> response described. Like, -exec-finish produces function-finished.

That would be good, I think.

> However, the user won't know when you get 'read-watchpoint-trigger'.
> What do you think? and if so, how would that fit into this description?
> Another table perhaps?

Why not mention that with each @item in the table you already added?
That is, under "@item function-finished" mention -exec-finish.

> +@item function-finished
> +An -exec-finish or similar CLI command was accomplished.

CLI commands such as -exec-finish should be in @code.

Otherwise, this can go in (provided that the code patch was approved).

Thanks.