From: Tom Tromey <tromey@redhat.com>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb ml <gdb@sourceware.org>
Subject: Re: Fwd: Addresses in pretty-printing
Date: Mon, 19 Nov 2012 21:56:00 -0000 [thread overview]
Message-ID: <878v9xp88o.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAHgb+0mRE449yJwRN9OBuDMhXTdRmuH_pq0CfFd2JoJAWf4XJg@mail.gmail.com> (Jim Blandy's message of "Sun, 18 Nov 2012 23:11:28 -0800")
>>>>> "Jim" == Jim Blandy <jimb@red-bean.com> writes:
Jim> Here is proposed documentation for gdb.Value.format, and two
Jim> accompanying functions, gdb.value_print_options and
Jim> gdb.set_value_print_options. I'd be willing to implement something
Jim> like this.
It seems like a worthwhile facility to me.
I think one possible objection is that this kind of thing will let
pretty-printer authors effectively override user settings. However,
we've see that they already do this, and it isn't really possible (or
perhaps arguably desirable) to stop them. Your proposal makes the
resulting code cleaner and is also, I think, useful for writing
new commands.
Jim> @findex gdb.set_value_print_options
Jim> @defun gdb.set_value_print_options (options)
Jim> Set the value printing options as given in @var{options}, a dictionary
Jim> whose items' keys name value printing options, and whose values are
Jim> the values to which those options should be set. Permitted keys are as
Jim> for @code{gdb.value_print_options}, described above.
This is just shorthand for a bunch of calls to gdb.execute, to set the
various parameters?
Tom
next prev parent reply other threads:[~2012-11-19 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHgb+0=pttEZ2uOcO6xfqJ4yvnzCCTJs0DTAZgLKKKwgZiocQQ@mail.gmail.com>
2012-11-19 7:11 ` Jim Blandy
2012-11-19 21:56 ` Tom Tromey [this message]
2012-11-19 23:03 ` Jim Blandy
2012-11-20 20:58 ` Tom Tromey
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=878v9xp88o.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.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