Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: obsoleting the annotate level 2 interface
Date: Tue, 21 Jan 2003 16:15:00 -0000	[thread overview]
Message-ID: <3E2D7205.3080100@redhat.com> (raw)
In-Reply-To: <vt265sjj6vi.fsf@zenia.red-bean.com>

> GDB seems to support two different ways of doing detailed annotations
> of its output for consumption by other programs: MI and 'set annotate
> 2'.  I don't think annotation level 2 has many active users, if any at
> all.  It pervades GDB's code.  Would it make sense to put 'set
> annotate 2' on the path to obsolescence?

Hmm, yes!  Dead code elimination is always good.
Removing the annotate stuff was always part of MI's long term agenda.

> Some background: the 'set annotate' command sets the
> 'annotation_level' variable.  There are only three distinguished
> values for this variable:

Can you perhaps do a little more research into the history of this 
feature?   For instance, was this initially part of some now abandoned 
project, or was this just `a good idea at the time'?  What of the other 
potential clients (DDD, ...)?  This helps strengthen the non-technical 
rationale for this user interface change.

As for implementing this, the first step is pretty easy, just tweak 
"main.c" to print a warning when level 2 is selected.  (Like the 
`deprecate mechanism we've got for commands'.)

> Personally, I'd like to see Emacs switch from annotation level 1 to
> MI, too; then we could get rid of annotation altogether.  But I think
> it makes sense to tackle level 2 first, since I don't think it has
> many users (if any).

Yes.  RMS has previously inidicated his liking of the idea of having 
EMACS use MI.  The lack of a console was identified as a technical 
barrier to that change :-/

Andrew



  reply	other threads:[~2003-01-21 16:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21  7:38 Jim Blandy
2003-01-21 16:15 ` Andrew Cagney [this message]
2003-01-21 16:54 ` David Carlton
2003-01-21 19:04 ` Eli Zaretskii
2003-01-22  8:37 ` Pierre Muller
2003-01-22 15:06   ` Elena Zannoni
     [not found] ` <15917.39229.935851.920452@nick.uklinux.net>
2003-01-28 20:51   ` Jim Blandy
2003-01-29  1:41     ` Nick Roberts
2003-01-29  5:37       ` Andrew Cagney
2003-01-29  5:40       ` Andrew Cagney
2003-01-29 21:58         ` Jim Blandy
2003-01-29 22:00           ` Arnaud Charlet
2003-01-29 22:50           ` Andrew Cagney
2003-01-29 21:52       ` Jim Blandy
2003-01-21 17:41 Michael Elizabeth Chastain
2003-01-21 20:25 ` David Carlton
2003-01-22 16:45 ` Andrew Cagney
2003-01-21 18:09 Michael Elizabeth Chastain
2003-01-22  7:56 ` Arnaud Charlet
     [not found] <1043140716.4941.ezmlm@sources.redhat.com>
2003-01-21 19:03 ` Jim Ingham
2003-01-21 20:40 Michael Elizabeth Chastain
2003-02-04  1:45 Mike Mueller
2003-02-04  6:58 ` Andrew Cagney

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=3E2D7205.3080100@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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