Re: RFC: MI output during program execution

[Jim Ingham <jingham@apple.com>]

Eli,

You don't want to run ALL cli commands through the mi command  
equivalents because then the output would come out in mi form, not  
cli form.  You really want to try to maintain the fidelity of the  
original CLI command even when running them under the MI, or the  
user's experience with the console will be disconcerting.  I think  
that's why Nick only grabbed the ones he wants to get information from.

But as I said in my previous note, I think a better solution is to  
use hooks/observers/events or whatever to allow the MI to be informed  
about things it needs to know about "behind the back" of the CLI  
that's running the command.  This is pretty easy to do - at least  
with hooks it is, I haven't converted our code over to observers -  
and means you don't need to go command by command, which would be a  
PITA indeed, and as I said would lose with user-defined commands in  
any case...

Jim


On Aug 9, 2005, at 9:37 AM, gdb-patches-digest- 
help@sources.redhat.com wrote:

> I'm a bit nervous about this literal testing of certain commands: why
> not allow _any_ CLI commands to be supported in this way?  I
> understand that you were trying to mention every command that runs the
> inferior, but the implication is that we will need to remember to add
> to this list any new command that has similar effects.  That sounds
> like a PITA; could a more general solution be devised?
>
> But I'm afraid that I'm somehow missing something, so could you please
> elaborate on the design of the solution you propose?
>
>
>