From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Formatting of function pointer value
Date: Mon, 11 Jul 2005 07:06:00 -0000 [thread overview]
Message-ID: <17106.5796.850869.491390@farnswood.snap.net.nz> (raw)
In-Reply-To: <dat0jr$kuh$3@sea.gmane.org>
> > It is a feature, not a bug. Why is your frontend using the
> > command-line interface?
>
> Well, the debugger part in KDevelop was not written by me, so I don't know
> why command-line interface, and not MI is used.
>
> > DON'T do that! Use MI nowadays, please please
> > please.
>
> I'm sorry, but section 24 of gdb manual does not say why MI is better. Can
> you give the reasons?
CLI output is intended for the user. It can change with a new release, and on
the state of execution in ways which are not easy to anticipate without
reading the source code. Provided that it still makes sense, that is not a
problem to the user but it can be to a frontend, if it is trying to parse the
output in a very precise manner. MI has a more formal syntax and so is not as
variable. Once it is fully developed, its output should be stable and if it
does change, some backward compatibility will probably be maintained.
Nick
next prev parent reply other threads:[~2005-07-11 7:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 8:02 Vladimir Prus
2005-07-08 8:51 ` Vladimir Prus
2005-07-08 13:59 ` Daniel Jacobowitz
2005-07-11 5:40 ` Vladimir Prus
2005-07-11 7:11 ` Vladimir Prus
2005-07-11 8:35 ` Andreas Schwab
2005-07-11 13:03 ` Daniel Jacobowitz
2005-07-08 13:58 ` Daniel Jacobowitz
2005-07-11 5:38 ` Vladimir Prus
2005-07-11 7:06 ` Nick Roberts [this message]
2005-07-11 7:21 ` Vladimir Prus
2005-07-11 7:42 ` Vladimir Prus
2005-07-11 13:08 ` Daniel Jacobowitz
2005-07-11 13:21 ` Vladimir Prus
2005-07-11 13:27 ` Daniel Jacobowitz
2005-07-14 8:10 ` Vladimir Prus
2005-07-11 8:08 ` Nick Roberts
2005-07-11 9:05 ` Vladimir Prus
2005-07-11 9:53 ` Nick Roberts
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=17106.5796.850869.491390@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).