From: Tom Tromey <tromey@redhat.com>
To: <Paul_Koning@Dell.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [Python] Allow attribute references to gdb.Value objects
Date: Mon, 15 Aug 2011 20:43:00 -0000 [thread overview]
Message-ID: <m3pqk6csop.fsf@fleche.redhat.com> (raw)
In-Reply-To: <09787EF419216C41A903FD14EE5506DD0151D58146@AUSX7MCPC103.AMER.DELL.COM> (Paul Koning's message of "Mon, 15 Aug 2011 15:29:55 -0500")
>>>>> "Paul" == <Paul_Koning@Dell.com> writes:
Paul> That's a fair point, but it comes at the expense of making the code
Paul> look rather un-Pythonic. It seems reasonable to offer the option, and
Paul> document the fact that code that takes advantage of it may be affected
Paul> by new built-in attributes.
My reasoning is that we want to encourage robust pretty-printers (a main
use of the value API), and robust code has to use the dictionary syntax.
So, why not just enforce this by only having the dictionary syntax?
Tom
next prev parent reply other threads:[~2011-08-15 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 19:33 Paul Koning
2011-08-15 19:09 ` Tom Tromey
2011-08-15 20:30 ` Paul_Koning
2011-08-15 20:43 ` Tom Tromey [this message]
2011-08-15 20:54 ` Paul_Koning
2011-08-16 1:12 ` Daniel Jacobowitz
2011-08-16 10:48 ` Paul_Koning
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=m3pqk6csop.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Paul_Koning@Dell.com \
--cc=gdb-patches@sourceware.org \
/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