This is the mail archive of the
mailing list for the GDB project.
Re: Strangeness in set command
> From: Michael Snyder <firstname.lastname@example.org>
> Cc: Eli Zaretskii <email@example.com>, Andreas Schwab <firstname.lastname@example.org>, email@example.com
> Date: Mon, 07 Apr 2008 12:05:59 -0700
> The problem is that "so long as it is not ambiguous"
> is dicy, and changes over time as we add new subcommands
> to "set".
> The shortcut is probably one of those "seemed like a
> good idea at the time" things, but now it's established
> and we're stuck with it.
> It would probably be a good idea if, every time we parse
> a "set" command, we try to match it with BOTH a variable
> AND a subcommand, and if there is ambiguity we say so
Or maybe, if the text after "set " has a `=' character in it, we
should ask whether the user really meant "set variable". IOW, refuse
to obey this shortcut, even if it's unambiguous.