From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Hooks still needed for annotations
Date: Sun, 03 Jul 2005 16:39:00 -0000 [thread overview]
Message-ID: <20050703163916.GB13811@nevyn.them.org> (raw)
In-Reply-To: <20050615225759.GA21803@white>
On Wed, Jun 15, 2005 at 06:57:59PM -0400, Bob Rossi wrote:
> > > > > Do you already use level 3, or could we simply just start stripping down
> > > > > level 2?
The point of introducing level 3 - a stripped down version of level 2 -
was to transition clients to using it and then discard level 2, instead
of having to find everyone using annotations and work out whether we
broke them every time someone wants to strip something out of level 2.
When everyone we care about is happy with level 3, we can kill level 2.
Bob, sometimes I feel like you pick very strange things to label as
"hard". What's hard about autodetecting the availability of annotate
level 3? Or even doing it based on version number?
> > > > Keeping level 3 allows a transition stage, I would now like to use it for
> > > > breakpoints-invalid and frames-invalid as stated above, in case I suddenly
> > > > find that Emacs does need them.
> > >
> > > Well breakpoints-invalid and frames-invalid already work (kind of) in
> > > a2. There is no reason to deprecate a2 and then get the same
> > > functionality in a3. (Although I might be missing something?). I really
> > > think that adding an a3 interface is a real bad idea.
> >
> > Level 3 has a reduced functionality. You've already said you think its a bad
> > idea, I'm trying to explain why I don't agree. I'm not adding it, its
> > already there.
>
> OK. Thanks for keeping me up to speed. I was under the impression that
> level 2 was going to go away completly and level 3 would be the
> temporary replacement. If level 2 stays (even though it's reduced), it
> would be completly fine with me.
Annotations are going to go away. Period. Not yet - not until we
agree that MI is ready - but I expect level 2 to go away before level
3.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-03 16:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 7:15 Nick Roberts
2005-06-01 11:30 ` Bob Rossi
2005-06-01 21:31 ` Nick Roberts
2005-06-03 19:09 ` Daniel Jacobowitz
2005-06-03 22:35 ` Nick Roberts
2005-06-03 23:59 ` Daniel Jacobowitz
2005-06-04 3:19 ` Nick Roberts
2005-07-03 17:03 ` Daniel Jacobowitz
2005-07-03 22:13 ` Nick Roberts
2005-07-03 22:44 ` Daniel Jacobowitz
2005-06-04 13:02 ` Bob Rossi
2005-06-13 3:14 ` Daniel Jacobowitz
2005-06-15 15:52 ` Bob Rossi
2005-06-15 16:07 ` Daniel Jacobowitz
2005-06-15 16:31 ` Bob Rossi
2005-07-03 16:45 ` Daniel Jacobowitz
2005-06-15 23:07 ` Nick Roberts
2005-06-15 23:29 ` Bob Rossi
2005-07-01 0:21 ` Bob Rossi
2005-07-01 1:18 ` Nick Roberts
2005-06-06 21:57 ` Nick Roberts
2005-06-10 2:26 ` Bob Rossi
2005-06-10 3:25 ` Nick Roberts
2005-06-15 15:24 ` Bob Rossi
2005-06-15 21:38 ` Nick Roberts
2005-06-15 22:58 ` Bob Rossi
2005-07-03 16:39 ` Daniel Jacobowitz [this message]
2005-07-06 15:03 ` Bob Rossi
2005-07-15 0:03 ` 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=20050703163916.GB13811@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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