From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Removal of markup annotations
Date: Wed, 28 Sep 2005 06:40:00 -0000 [thread overview]
Message-ID: <17210.15172.757495.813012@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20050928034539.GA29542@nevyn.them.org>
DJ> I'm indifferent on removing them entirely, but I support removing them
DJ> from level three. However other programs have definitely started to
DJ> use level 3 - e.g. google found clewn.sf.net/clewn.txt.html. Actually
DJ> that was the only one I could easily turn up. Want to double-check
DJ> that it doesn't use these?
Level 3 was intended as a transition to GDB/MI. clewn started as VimGDB
and I pointed out to Andrew Cagney that they were using annotations back
then.
http://article.gmane.org/gmane.editors.vim.devel/6069 shows some of that
dialogue:
> Date: 2004-03-29 12:59:10 GMT (1 year, 26 weeks, 11 hours and 26 minutes ago)
> The last patch #6 (soon on Mikolaj web site) supports GDB/MI and
> annotations level 3. It also provides hooks for a future
> implementation based on an interface with only GDB/MI.
> On Tue, 10 Feb 2004 5:32:52 PM EST, Andrew Cagney wrote:
> > It's been pointed out to me that VIM is using GDB's deprecated, never
> > documented, never tested, annotation level 2 interface. In a word,
> > argh!
> >
> > GDB developers are strongly encouraged to migrate their application to MI
> > (which is documented and is tested).
They also seem not to understand that level 3 annotations are just a subset
of level 2 and think that they are necessary to access GDB/MI.
> Clewn may run in two different modes called level 2 and level 3. Level 2 uses
> GDB annotations level 2. Level 3 uses GDB/MI and annotations level 3. The
> behaviour of |clewn-variables| is different, depending on the mode setting.
> When starting, Clewn automatically selects the appropriate mode.
They could just use level 2 and I don't think they can reasonably complain if
we remove two dysfunctional annotations from level 3.
Nick
next prev parent reply other threads:[~2005-09-28 6:40 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
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 [this message]
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=17210.15172.757495.813012@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.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