From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add the "-info-os" command to MI
Date: Thu, 27 Oct 2011 00:24:00 -0000 [thread overview]
Message-ID: <4EA892F4.3000302@earthlink.net> (raw)
In-Reply-To: <m3pqhqdqp4.fsf@fleche.redhat.com>
On 10/21/11 1:39 PM, Tom Tromey wrote:
>>>>>> ">" == Kwok Cheung Yeung<kcy@codesourcery.com> writes:
>>> + { "info-os", { "info os", 1 }, NULL },
> I'd prefer a new function specific to MI to do the command-line parsing.
>
> I think this approach should be deprecated and that no new instances go
> into the tree. They unnecessarily link MI to the CLI, making it harder
> to change the CLI.
>
I can see the appeal of the decoupling, but we share argument parsing
like this because there's not a lot of practical purpose to having two
parsers - once the command is out there and being used, we're loath to
change it much anyway. To me, the MI's main value is in avoiding cases
where CLI ambiguity and elision makes for a better user experience, but
in this case the arguments are data-driven by platform-specific code,
not much ambiguity involved.
Stan
next prev parent reply other threads:[~2011-10-26 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 15:52 Kwok Cheung Yeung
2011-10-13 16:13 ` Eli Zaretskii
2011-11-23 23:37 ` Kwok Cheung Yeung
2011-12-06 18:53 ` Pedro Alves
2011-10-21 20:53 ` Tom Tromey
2011-10-27 0:24 ` Stan Shebs [this message]
2011-10-27 16:45 ` Tom Tromey
2011-11-24 23:15 ` Kwok Cheung Yeung
2011-11-25 11:56 ` Eli Zaretskii
2011-11-29 19:01 ` Tom Tromey
2011-11-29 23:18 ` Kwok Cheung Yeung
2011-11-30 14:47 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA892F4.3000302@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox