From: Tom Tromey <tromey@redhat.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Patch: annotations -vs- deprecated hooks
Date: Mon, 14 Jul 2008 15:22:00 -0000 [thread overview]
Message-ID: <m3od508p9o.fsf@fleche.redhat.com> (raw)
In-Reply-To: <18554.44449.266149.362665@kahikatea.snap.net.nz> (Nick Roberts's message of "Mon\, 14 Jul 2008 13\:36\:33 +1200")
>>>>> "Nick" == Nick Roberts <nickrob@snap.net.nz> writes:
Nick> In Emacs, variables get marked as obsolete but they are rarely
Nick> removed from the code.
I think that makes a lot of sense for Emacs, because there are
millions of lines of elisp out there, and breaking those randomly
would be unfriendly.
I don't think this consideration applies to gdb, though.
Nick> Creating observers just for breakpoints results in a mixed
Nick> approach for annotations as others don't use observers and
Nick> removing the deprecated label might encourage their use.
Yes. I'm aware of the calls to annotate_* all over gdb, and the
strangely named "breakpoints_changed".
I have a followup patch to get rid of the latter. I didn't submit it
since it causes a test suite regression :). My approach was different
from yours in that I tried to piggy-back this on existing observers --
I'm basically trying to avoid adding observers at *every* place we
currently have a deprecated hook. Some of those places seem like odd
spots for a hook (e.g., breakpoints_changed is called from
set_raw_breakpoint, which somehow just seems wrong to me).
Anyway, I was not actually planning to look at annotate_*; I'm
ambivalent about my breakpoints_changed patch. I mostly wanted to get
rid of all the deprecated bits.
Nick> http://sourceware.org/ml/gdb-patches/2008-06/msg00000.html
Nick> http://sourceware.org/ml/gdb-patches/2008-06/msg00012.html
Nick> http://sourceware.org/ml/gdb-patches/2008-06/msg00018.html
Oh, sorry about this. I remembered these patches vaguely but didn't
realize how much overlap there was with my cleanups.
Anything implemented twice like this must be a good idea :-)
Tom
next prev parent reply other threads:[~2008-07-14 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 21:59 Tom Tromey
2008-07-13 22:26 ` Nick Roberts
2008-07-13 23:15 ` Tom Tromey
2008-07-14 0:20 ` Nick Roberts
2008-07-14 0:50 ` Tom Tromey
2008-07-14 0:57 ` Daniel Jacobowitz
2008-07-14 1:37 ` Nick Roberts
2008-07-14 15:22 ` Tom Tromey [this message]
2008-07-14 5:00 ` Joel Brobecker
2008-07-14 17:27 ` Joel Brobecker
2008-07-14 17:46 ` Tom Tromey
2008-07-16 12:42 ` Nick Roberts
2008-07-28 17:50 ` Tom Tromey
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=m3od508p9o.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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