From: Jim Ingham <jingham@apple.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Add fullname to breakpoint output
Date: Sat, 05 Apr 2003 17:59:00 -0000 [thread overview]
Message-ID: <540DA746-6790-11D7-958C-000A277A8808@apple.com> (raw)
In-Reply-To: <3E8F124E.2010807@redhat.com>
On Saturday, April 5, 2003, at 09:28 AM, Andrew Cagney wrote:
>
>> 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.
>
Yes, this is a desirable goal. Have you thought about how to do this?
The best way I can think of is to have a new ui_out that builds up an
intermediate representation for results that is easy to access randomly
- making up real lists & dictionaries from the ui_out_field_xxx and
list & table stuff. Then we could banish ui_out_text & friends to the
CLI commands to take the whole result, pull bits out in the order they
expected, and annotate them with text, newlines, etc, in order to make
a nice display.
In practice, this will be gnarly to get right, but you could do it
incrementally by getting the intermediate rep. ui_out working, then fix
the CLI commands one by one by swapping in the new ui_out for those
commands you had fixed, and using the old CLI one for the commands you
hadn't gotten working...
Idle Saturday speculation, maybe...
Jim
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham
jingham@apple.com
Developer Tools - gdb
next prev parent reply other threads:[~2003-04-05 17:59 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
2003-04-05 17:59 ` Jim Ingham [this message]
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=540DA746-6790-11D7-958C-000A277A8808@apple.com \
--to=jingham@apple.com \
--cc=ac131313@redhat.com \
--cc=gdb@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