Quoting, backslashes, CLI and MI

[Eli Zaretskii]

> Date: Wed, 22 Feb 2006 09:29:53 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sourceware.org
> 
> -exec-arguments ARGS; should it take a single string which is then
> split by buildargv into a vector, or should it take freeform text which
> is then split into an argument vector?  Well, right now it takes a
> literal string, since it just passes the text to CLI "set args". 
> That's saved as a string and then passed to create_inferior as a
> string, and eventually passed directly to a shell in the fork-child.c
> case.  So, as un-MI-like as it is, I think I'd have to leave this one
> alone for now - it's just too big a can of worms!

We should leave it alone, and not only because it's a mess:
"-exec-arguments" _should_ pass its argument to the shell, it should
not second-guess the shell features, nor reinvent them.