Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb@sources.redhat.com, bob_rossi@cox.net
Subject: Re: [rfc] Annotation level THREE
Date: Fri, 21 Mar 2003 19:22:00 -0000	[thread overview]
Message-ID: <3E7B6667.6030805@redhat.com> (raw)
In-Reply-To: <15995.20665.215224.490948@nick.uklinux.net>

>  > > Perhaps I could turn that question round. Which annotations are you planning
>  > > to keep?
>  > 
>  > I think annotations can be split into two categores:
>  > 
>  > - events
>  > These let GDB notify the GUI of internal state changes.
>  > 
>  > - markups
>  > These try to make CLI output, intended solely for a human, machine parsable.
>  > 
>  > The events remain (target changed, breakpoint created, ....).  The 
>  > markups are removed (*-{begin,end})
> 
> I would like to try this approach. Firstly for pragmatic reasons: this is
> what is being offered. Secondly, it will give me a chance to experiment with
> things like variable objects.
> 
> I have just one question:
> 
> How long do you expect level 3 annotations would remain in GDB?

How long is a piece of string?

Seriously.

Since the event notifications don't intrude into the CLI, and the new 
underlying event mechanism (observer.[hc]) is common to both annotations 
and the MI, I don't see there being a compelling reason to remove that 
mechanism (it's maintenance overhead is very low).

Contrast that to the markups that GDB is pushing hard to remove.  Their 
implementation intrudes badly into the CLI and hence, make it hard for 
GDB developers to consider even minor changes (for fear of breaking a 
GUI :-().

Andrew



  reply	other threads:[~2003-03-21 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E6E7326.3020906@redhat.com>
     [not found] ` <15985.7336.23998.590592@nick.uklinux.net>
     [not found]   ` <3E751565.4030409@redhat.com>
     [not found]     ` <15990.10811.61395.996906@nick.uklinux.net>
     [not found]       ` <3E763228.9060104@redhat.com>
     [not found]         ` <15990.62618.114706.459904@nick.uklinux.net>
     [not found]           ` <3E774292.8070603@redhat.com>
2003-03-21 17:53             ` Nick Roberts
2003-03-21 19:22               ` Andrew Cagney [this message]
     [not found]           ` <3E773B59.90403@redhat.com>
2003-03-27 20:51             ` Nick Roberts
2003-03-28 22:30               ` Andrew Cagney
2003-03-30 14:59                 ` variable objects (was: [rfc] Annotation level THREE) Nick Roberts
2003-03-30 15:11                   ` Andrew Cagney
2003-03-31  9:01                     ` Jason Molenda

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=3E7B6667.6030805@redhat.com \
    --to=ac131313@redhat.com \
    --cc=bob_rossi@cox.net \
    --cc=gdb@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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