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
Subject: Re: GDB/MI revisited
Date: Mon, 03 Mar 2003 19:09:00 -0000	[thread overview]
Message-ID: <3E63A84A.4030407@redhat.com> (raw)
In-Reply-To: <15970.39290.513649.825076@nick.uklinux.net>

>  
>  > > I would prefer this approach too since the GUD buffer would then allow
>  > > completion. However, without level 2 annotations, the CLI is useless to the
>  > > lisp package that I have written, so I don't see how an incremental migration
>  > > is possible.
>  > 
>  > Why exactly is it useless?  Using both [deprecated] level 2 annotations 
>  > and "interpreter mi ..." simultaneously.
> 
> Ah! I follow you now. Does this mean that you would like to incrementally
> obsolete annotations? This relates to something that I said earlier:

There is always room for both compromize and reality :-)

> If this is the case, I *think* I could modify gdb-ui.el not to use the
> annotation breakpoints-invalid quite easily. I don't know what other users
> of level 2 annotations, e.g the authors of cgdb, would think, though.

What about defining `level three' annotations as the event stuff from 
level two but with all the breakpoint et.al. markups removed?

Having the CLI generate event annotations is hardly different to having 
MI generate it's event messages.

Andrew



  parent reply	other threads:[~2003-03-03 19:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 20:20 Nick Roberts
2003-02-26 16:21 ` Andrew Cagney
2003-02-28 21:35   ` Nick Roberts
2003-03-02  2:35     ` Andrew Cagney
2003-03-02 23:57       ` Nick Roberts
2003-03-03  1:04         ` Bob Rossi
2003-03-03 19:09         ` Andrew Cagney [this message]
2003-03-03 20:44           ` Nick Roberts
2003-03-04  0:12             ` 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=3E63A84A.4030407@redhat.com \
    --to=ac131313@redhat.com \
    --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