Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Another annotation for threads
Date: Fri, 06 Jun 2008 06:59:00 -0000	[thread overview]
Message-ID: <20080606065909.GC3602@adacore.com> (raw)
In-Reply-To: <18504.36031.91267.352783@kahikatea.snap.net.nz>

> It might be construed as bad attitude but I don't really understand why
> there is so much concern about such a small change that will only impact
> thosee who use GDB from Emacs.

I don't personally consider this bad attitude, as you had some technical
arguments in favor of your approach. I balanced the various advantages
and drawbacks of both approaches, and judged that, although I would have
still prefered us to use observers, your approach was an acceptable
temporary compromise (temporary meaning until annotation are removed).
One of the elements on which I based my judgement was the fact that
I understood that this was going to be the only new annotation.

> A while ago (three years actually) I submitted a patch to remove far more
> markup than I am adding:
> 
> http://sourceware.org/ml/gdb-patches/2005-06/msg00189.html
> 
> but there was no interest.  
> 
> It started from a dialogue with Andrew Cagney to relieve some of the
> pressure to remove the remaining annotations but only drew a response
> from Bob Rossi.  I think we concluded that the breakpoints-invalid and
> frames-invalid annotations could go.  So I'll offer now to submit
> another patch just to remove those twoannotations (which fired far too
> often, anyway).  This should more than make up for the two I've just
> added.

My perspective on this is that I would like to see as little effort
spent on annotations as possible. If you think the change is going
to make GDB better, then perhaps your suggestion is worth it. If it's
just to reduce the pressure to remove annotations from GDB, then
I think we need to look at the maintenance cost of keeping them in.
If possible, I'd rather remove them all in one go rather than remove
some of them in exchange for the new ones being added.

I don't know the annotations well enough to know what the actual impact
might be.  They might make GDB better.  But I'm quite concerned about
the front ends out there that might be relying on some the annotations
that are proposed to be removed.

-- 
Joel


  reply	other threads:[~2008-06-06  6:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  6:13 Nick Roberts
2008-05-21  8:54 ` Eli Zaretskii
2008-06-05 19:30 ` Daniel Jacobowitz
2008-06-05 21:20   ` Nick Roberts
2008-06-05 21:26     ` Daniel Jacobowitz
2008-06-05 22:02       ` Joel Brobecker
2008-06-06  1:03         ` Nick Roberts
2008-06-06  6:59           ` Joel Brobecker [this message]
2008-06-06  0:50       ` Nick Roberts
2008-06-06  1:06         ` Tom Tromey
2008-06-06  2:30           ` Daniel Jacobowitz
2008-06-06  2:44             ` Tom Tromey
2008-06-06  2:39         ` Pedro Alves
2008-06-06  3:00           ` Nick Roberts
2008-06-06 11:44             ` 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=20080606065909.GC3602@adacore.com \
    --to=brobecker@adacore.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