From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: MI fine-grained versioning
Date: Mon, 18 Dec 2006 15:47:00 -0000 [thread overview]
Message-ID: <20061218154737.GA9119@nevyn.them.org> (raw)
In-Reply-To: <200612181835.34025.vladimir@codesourcery.com>
On Mon, Dec 18, 2006 at 06:35:33PM +0300, Vladimir Prus wrote:
> Yet another approach is to "detect" presence of feature by trying some commands,
> or by trying commands with some new options, or by constructing more contrived test
> cases. However that's troublesome.
>
> How about adding new MI command that returnes list of supported fine-grained features.
> For example:
>
> -list-features
> ^done,result=["frozen_variables","info_path_expression"]
>
> The MI manual would contain a section listing all feature names and briefly documenting them.
>
> Comments?
If you want to do this, it sounds like this is the right way - compare
to the qSupported I recently added for the remote protocol. I guess
this is the logical place to add a list of supported MI versions,
too...
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-12-18 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 15:35 Vladimir Prus
2006-12-18 15:39 ` Bob Rossi
2006-12-18 16:02 ` Vladimir Prus
2006-12-18 19:52 ` Nick Roberts
2006-12-18 19:56 ` Bob Rossi
2006-12-18 15:47 ` Daniel Jacobowitz [this message]
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=20061218154737.GA9119@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@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