From: Nick Roberts <nickrob@snap.net.nz>
To: Bob Rossi <bob@brasko.net>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Hooks still needed for annotations
Date: Fri, 10 Jun 2005 03:25:00 -0000 [thread overview]
Message-ID: <17065.2154.827857.784226@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050610022625.GA6660@white>
Bob Rossi writes:
> On Tue, Jun 07, 2005 at 09:57:48AM +1200, Nick Roberts wrote:
> >
> > > They are deprecated. I believe there's a clear consensus that the
> > > entire annotation system is going to go, and in the near future. Just
> > > not yet.
> >
> > Then lets try to remove the ones that can go. In 2003 Andrew introduced
> > level 3 annotations as a subset of level 2 (with the markup annotations
> > left out). Since then I have been using those quite happily with Emacs.
> >
> > So, as far as Emacs is concerned, the annotations that are restricted to
> > level 2 in annotate.c, and this must be over half of them, can go.
> >
> > Bob is this also the case for CGDB?
>
> I could look and see what annotations CGDB uses. Would this be helpful?
> I think it's only a handful.
Well there hasn't been any interest shown from the global maintainers, but I
think it would be helpful. Do you need any of the annotations that are
not generated by level 3 annotations? (Specified by
if (annotation_level == 2)... in annotate.c)
> > Emacs doesn't use breakpoints-invalid or frames-invalid either and they
> > spew out so often that it makes it hard to interrupt the inferior. However
> > I would like to keep them for the moment, as they provide clues as to where
> > to put code for event nortification in MI. Perhaps these could be restricted
> > to level 2.
>
> I still use level 2, and personally thought introducing level 3 was a
> really bad idea.
Why is it a bad idea?
> Do you already use level 3, or could we simply just start stripping down
> level 2?
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.
Nick
next prev parent reply other threads:[~2005-06-10 3:25 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 [this message]
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
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=17065.2154.827857.784226@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob@brasko.net \
--cc=drow@false.org \
--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