From: Doug Evans <xdje42@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Phil Muldoon <pmuldoon@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
guile-user@gnu.org
Subject: Re: [PATCH 00/13] script language API for GDB
Date: Mon, 23 Dec 2013 17:40:00 -0000 [thread overview]
Message-ID: <CAP9bCMS+7czK5Si92b_2zO3Eo0Emn_b8MQDAv9aVKBCpgfGsLw@mail.gmail.com> (raw)
In-Reply-To: <87sitnij45.fsf@fleche.redhat.com>
[+ guile-user
For background: https://sourceware.org/ml/gdb-patches/2013-12/msg00243.html ]
On Fri, Dec 20, 2013 at 8:26 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <xdje42@gmail.com> writes:
>
> Doug> One thought I have for this is "info guile pretty-printer", etc.
> Doug> That simplifies a lot of things. From a u/i perspective it has
> Doug> both plusses and minuses, but I like it overall.
>
> The problem with this approach is that it assumes that the user both
> knows and cares in which extension language a given feature is
> implemented. However, I don't believe either of those is true in the
> most common situations. My experience with the libstdc++ printers is
> that most people want them to "just work" and that any amount of
> required under-the-hood knowledge is too much of a burden.
OTOH, there are situations where a user can care.
For those that don't care, "info pretty-printer" can still print all of them.
"info pretty-printer" et.al. would need some work, sure, and one way
to go would be to use
"info <ext-lang> pretty-printer".
next prev parent reply other threads:[~2013-12-23 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 17:06 Doug Evans
2013-12-06 5:51 ` Doug Evans
2013-12-06 12:57 ` Phil Muldoon
2013-12-06 16:07 ` Doug Evans
2013-12-20 16:26 ` Tom Tromey
2013-12-23 17:40 ` Doug Evans [this message]
2013-12-23 21:54 ` Tom Tromey
2013-12-23 21:58 ` Doug Evans
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=CAP9bCMS+7czK5Si92b_2zO3Eo0Emn_b8MQDAv9aVKBCpgfGsLw@mail.gmail.com \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=guile-user@gnu.org \
--cc=pmuldoon@redhat.com \
--cc=tromey@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