This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: About multi-inferior commands
- From: Pedro Alves <pedro at codesourcery dot com>
- To: Michael Snyder <msnyder at vmware dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>, "tromey at redhat dot com" <tromey at redhat dot com>
- Date: Fri, 25 Feb 2011 13:27:40 +0000
- Subject: Re: About multi-inferior commands
- References: <4D67043C.9000509@vmware.com>
On Friday 25 February 2011 01:22:04, Michael Snyder wrote:
> I want to say, this has been my first opportunity to try out the
> multi-inferior commands, and I am impressed! Nice work!
Yay!
> I have a question -- I would like to get-number-ify the commands
> "inferior", kill inferior, detach inferior, remove inferior, etc.
> However, you have implemented them in terms of parse_and_eval_long,
> which is actually more powerful. It handles full expressions.
>
> So if I go ahead, the trade off is that we will gain lists and
> ranges, but lose expressions and user variables. What do you
> think about that? Is it too late for such a change?
Well, "info breakpoints" used to take a parse_and_eval_long
as well, and it's a much older command :-P. So did
"info inferiors", and other commands we've been changing
the last few days...
IMO, it's fine. You can still do
set $foo = <expression>
command $foo
instead of
command <expression>
IIUC.
--
Pedro Alves