Re: Make -exec-run and -exec-until into 'real' MI commands

[Vladimir Prus <vladimir@codesourcery.com>]

On Wednesday 13 January 2010 23:26:21 Daniel Jacobowitz wrote:

> On Wed, Jan 13, 2010 at 11:13:24PM +0300, Vladimir Prus wrote:
> > I think that only "\"" won't be preserved. While "a b" will be present in reconstructed
> > string with quotes.
> 
> Won't we have problems with Windows paths, for example?
> 
> -exec-run 'c:\My Documents\test' "c:\My Documents\test"
> 
> % exec /usr/bin/gdb 'c:\My Documents\test' "c:\My Documents\test"
> 
> But the MI parser is going to turn that second \t into a tab
> if I'm not mistaken.  This is a really hard transformation to
> reverse.
> 
> > I believe the fact that no known frontends use args was raised the last time,
> > but you still wanted to assume they exist.
> 
> Blech, I hate having to argue with myself.
> 
> I suggest asking for a second opinion then.  I don't think this
> quoting is good enough to be a good idea.  I think we can get away
> without it for -exec-run.  I don't know about -exec-until.

Apparently, nobody seem to have a second opinion :-(
So, unless I hear objections by tomorrow, I will commit a patch that:

a) make -exec-run refuse to accept any parameters, as no frontend
that cares is known.
b) does nothing with -exec-until, since your point about \t seems like
a killer. I'll fix -exec-until for MI3, whenever that comes around.


Thanks,

-- 
Vladimir Prus
CodeSourcery
vladimir@codesourcery.com
(650) 331-3385 x722