From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: [BUG:MI] -break-list doesn't list multiple breakpoints
Date: Tue, 15 Jan 2008 17:08:00 -0000 [thread overview]
Message-ID: <fmipa3$6vf$1@ger.gmane.org> (raw)
In-Reply-To: <18311.64973.546980.107837@kahikatea.snap.net.nz>
Nick Roberts wrote:
> > > I'm not sure of the logic of committing an incomplete patch, but in
> > > any case I think this needs to be fixed before the next release.
> >
> > I disagree. If someone needs this functionality in MI, they are
> > invited to contribute it. Unless I'm completely mistaken, what
> > happened previously in MI was even worse.
>
> Multiple breakpoints are new, so nothing happened in MI previously did it?
> The format of CLI output for pending breakpoints has currently changed and
> in that context Vladimir said:
>
> ...And probably the only way to change the situation is to decide that
> MI is the future, and actively discourage use of CLI for anything, to
> the degree of immediately refusing any request mentioning CLI in
> relation to any frontend.
>
> Refusing requests mentioning CLI and not providing functionality in MI
> seems to leave the frontend developer between a rock and a hard place.
As a meta-comment, I'd like to point out that I'm a frontend developer,
and I'm in no better position than you in anyway.
Now, what do you want -- making sure that all new functionality is available
via MI, or that it's available via CLI? Of course "both CLI and MI" is
a possible answer, but it increases the amount of work and the time till
completion.
- Volodya
next prev parent reply other threads:[~2008-01-15 17:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 22:08 Nick Roberts
2008-01-11 17:36 ` Vladimir Prus
2008-01-11 21:34 ` Nick Roberts
2008-01-11 22:55 ` Daniel Jacobowitz
2008-01-11 23:38 ` Nick Roberts
2008-01-15 17:08 ` Vladimir Prus [this message]
2008-01-15 21:38 ` Nick Roberts
2008-01-13 21:26 ` Nick Roberts
2008-01-29 19:16 ` Daniel Jacobowitz
2008-01-29 22:53 ` Nick Roberts
2008-01-29 23:31 ` Daniel Jacobowitz
2008-01-30 0:52 ` Nick Roberts
2008-01-30 3:04 ` Nick Roberts
2008-01-30 3:20 ` Daniel Jacobowitz
2008-01-30 5:59 ` Vladimir Prus
2008-01-30 7:14 ` Nick Roberts
2008-01-30 7:32 ` Vladimir Prus
2008-01-30 7:50 ` Nick Roberts
2008-01-30 7:58 ` Vladimir Prus
2008-02-01 20:15 ` Marc Khouzam
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='fmipa3$6vf$1@ger.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb-patches@sources.redhat.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