This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: "set" command with 2 arguments instead of one?
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Doug Evans <xdje42 at gmail dot com>
- Cc: "Tedeschi, Walfred" <walfred dot tedeschi at intel dot com>, Andreas Schwab <schwab at linux-m68k dot org>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Mon, 20 Apr 2015 08:25:33 -0700
- Subject: Re: RFC: "set" command with 2 arguments instead of one?
- Authentication-results: sourceware.org; auth=none
- References: <20141123042417 dot GA839 at adacore dot com> <87bnny45zi dot fsf at igel dot home> <20141123095317 dot GE5774 at adacore dot com> <CAP9bCMStR=uJ387HDhKdN8CHShFOiquYFHXhOvcVX0i0_Hr7VA at mail dot gmail dot com> <20141124071258 dot GI5774 at adacore dot com> <AC542571535E904D8E8ADAE745D60B192FA0A7CD at IRSMSX104 dot ger dot corp dot intel dot com> <20150414124920 dot GH4704 at adacore dot com> <CAP9bCMT-2YOZGZ1HRuVWFoL+at7MmTiOWSFS7mH8AcUZyx2Jdw at mail dot gmail dot com>
> gdb is never going to be at a point where all commands can use buildargv.
> I think choosing either buildargv or commas (using parse_to_comma_and_eval
> or whatever) should consider what the arguments to the command are.
> And since this command takes things that are more like expressions
> than like strings, I'm leaning towards commas.
OK with me.
--
Joel