From: Nick Roberts <nickrob@snap.net.nz>
To: Bob Rossi <bob_rossi@cox.net>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb@sources.redhat.com
Subject: Re: MI fine-grained versioning
Date: Mon, 18 Dec 2006 19:52:00 -0000 [thread overview]
Message-ID: <17798.61527.726165.630956@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061218153921.GY20942@cox.net>
> > 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.
>
> Great idea!
>
> There are a few gothcha's. For instance, each command can support
> several parameters, so you might want to report on that. But more
> tricky, is when a command adds an output field that the front end cares
> about.
In the manual we already explain that front ends should be able to handle
extra fields in MI output. The front end would need to do this just
to handle -list-features.
> An example of this would be that the -break-list command has
> always existed, but the -break-list command added fullpath functionality
> later on it it's life. How would you handle this, if at all?
Clearly it can't be retrospective. I think it's a good idea and would be
more convenient than bumping the level for small changes.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-12-18 19:52 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 [this message]
2006-12-18 19:56 ` Bob Rossi
2006-12-18 15:47 ` Daniel Jacobowitz
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=17798.61527.726165.630956@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob_rossi@cox.net \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.com \
/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