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 08:08:00 -0000 [thread overview]
Message-ID: <17106.10589.435150.575928@farnswood.snap.net.nz> (raw)
In-Reply-To: <dat662$nu$2@sea.gmane.org>
> > 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,
>
> So it's not stable yet?
The manual says:
Note that GDB/MI is still under construction, so some of the
features described below are incomplete and subject to change.
> > its output should be stable and if
> > it does change, some backward compatibility will probably be maintained.
>
> Ok, the the only advantage of MI is stable output format.
I've not said that. It also uses variable objects, it aims to be
asynchronous...
> Can you tell me how it's achieved?
As I've already said, it has a more formal syntax.
> For example, looking at the code that prints function values (what worries
> me in the first place):
>
> fprintf_filtered (stream, "{");
> type_print (type, "", stream, -1);
> fprintf_filtered (stream, "} ");
I don't understand the point of the example.
> As I right in assuming that exactly the same output will be produced for MI
> mode and for CLI mode?
No, you're wrong to assume that. That should be clear from the examples
in the manual.
Nick
> If so, then how MI can be more stable than CLI, if the output is the same?
next prev parent reply other threads:[~2005-07-11 8:08 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
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 [this message]
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.10589.435150.575928@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).