From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Removal of markup annotations
Date: Sun, 03 Jul 2005 22:45:00 -0000 [thread overview]
Message-ID: <20050703224525.GB26046@nevyn.them.org> (raw)
In-Reply-To: <17096.24639.940089.355645@farnswood.snap.net.nz>
On Mon, Jul 04, 2005 at 10:01:35AM +1200, Nick Roberts wrote:
> > > This patch cleans up the code quite considerably and hopefully will relieve
> > > some of the pressure to remove the remaining annotations.
> >
> > Is there "pressure"? I don't see the point in snipping out bits of
> > -annotate=2 until we're ready to remove it entirely, which I would like
> > to do but I accept that we are not yet ready for.
>
> Its hard for me to tell if the pressure is real or imagined. There _was_
> pressure two years ago (around Jan 2002) but the people involved aren't
> currently active on the mailing list. The idea behind level 3 annotations
> _was_ to allow snipping out a (large) bit of the sprinkled code for
> annotations. Its not a problem for me. If its not a problem for anyone else,
> then it might as well stay (although that does beg the question as to why
> it needs to be removed at all).
Eventually, we'll make changes to GDB that will make it hard to
preserve the structure of annotations. We've probably made several
already - an example is the interps.c change that you're talking about
fixing in another thread. The nature of annotations makes it hard to
preserve their reliability.
I just want to approach it from the other side. When MI is ready, or
we've got a patch that is otherwise good but hoses some annotations,
then let's start deleting them.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-03 22:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 3:19 Nick Roberts
2005-06-15 15:41 ` Bob Rossi
2005-06-15 23:07 ` Nick Roberts
2005-06-15 23:35 ` Bob Rossi
2005-06-15 23:58 ` Nick Roberts
2005-06-21 1:41 ` Bob Rossi
2005-06-21 6:00 ` Nick Roberts
2005-06-21 10:22 ` Bob Rossi
2005-06-16 3:28 ` Eli Zaretskii
2005-06-15 17:06 ` Eli Zaretskii
2005-06-15 21:41 ` Nick Roberts
2005-06-20 11:54 ` Nick Roberts
2005-06-20 19:29 ` Eli Zaretskii
2005-06-20 21:48 ` Nick Roberts
2005-06-21 3:41 ` Eli Zaretskii
2005-06-21 7:32 ` Nick Roberts
[not found] ` <uacljzbgq.fsf@gnu.org>
2005-06-21 23:47 ` Nick Roberts
2005-06-22 3:25 ` Eli Zaretskii
2005-06-22 6:22 ` Nick Roberts
2005-07-03 19:04 ` Daniel Jacobowitz
2005-07-03 22:13 ` Nick Roberts
2005-07-03 22:45 ` Daniel Jacobowitz [this message]
2005-09-28 0:17 ` Nick Roberts
2005-09-28 2:39 ` Bob Rossi
2005-09-28 3:45 ` Daniel Jacobowitz
2005-09-28 6:40 ` Nick Roberts
2005-09-28 13:11 ` Daniel Jacobowitz
2005-09-28 22:52 ` Nick Roberts
2005-09-28 22:56 ` 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=20050703224525.GB26046@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