From: Andrew Cagney <ac131313@redhat.com>
To: Jim Ingham <jingham@apple.com>
Cc: gdb@sources.redhat.com
Subject: Re: Add fullname to breakpoint output
Date: Sat, 05 Apr 2003 17:28:00 -0000 [thread overview]
Message-ID: <3E8F124E.2010807@redhat.com> (raw)
In-Reply-To: <8E93EF0A-66EB-11D7-A344-00039379E320@apple.com>
> In my view, the CLI should aim at minimalism, since a human being is scanning it and too much information would be confusing. The MI is intended to be scanned by a program, so we should feel free to cram in whatever might be useful - within reason of course... For this reason, when we found PB needed an extra bit of data which might not be so useful to the CLI user, we would just add it to the MI only. This is a little unsatisfying in implementation, since it means you have
>
> if (ui_out_is_mi_like (uiout))
> {
>
> }
>
> scattered through non-interpreter specific code. But this is better than cluttering up the CLI output for stuff that is more interesting to a front-end...
Just FYI, the current intermingling of CLI and MI code is short term -
get something working. Medium to long term, the two need to be more
cleanly separated. Related to this is separating more of the CLI from
core GDB.
Andrew
next prev parent reply other threads:[~2003-04-05 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1049485092.22026.ezmlm@sources.redhat.com>
2003-04-04 22:19 ` Jim Ingham
2003-04-05 17:28 ` Andrew Cagney [this message]
2003-04-05 17:59 ` Jim Ingham
2003-04-14 4:14 ` Andrew Cagney
2003-04-14 17:04 ` Jim Ingham
2003-04-04 19:38 Nick Roberts
2003-04-05 17:24 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-04-04 1:03 Bob Rossi
2003-04-03 1:26 Bob Rossi
2003-04-04 16:59 ` 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=3E8F124E.2010807@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jingham@apple.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