From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Python pretty-printing [3/6]
Date: Mon, 06 Apr 2009 23:26:00 -0000 [thread overview]
Message-ID: <m3eiw52wkx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090403163024.GB28512@caradoc.them.org> (Daniel Jacobowitz's message of "Fri\, 3 Apr 2009 12\:30\:24 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
>> +If @var{name} is given, it specifies the name of a type to look up in
>> +the inferior. @var{name} is searched for globally.
>> +@end defmethod
Daniel> So the constructor does a lookup. This will be a little weird if we
Daniel> want to create types from scratch someday (could be very useful).
At that point we can always make the constructor change its behavior
depending on the runtime type of the argument.
t = Type(gdb.STRUCT) # make a new struct, STRUCT is an int
t = Type("whatever") # look up "whatever"
Daniel> And what happens if name is not given?
This is some relic or misconception in the code... the name need not
be optional.
Daniel> Anyway, I wonder if there shouldn't be an explicit lookup
Daniel> routine instead.
I like it ok the way it is. But, if you really want it changed, I
will do that; now is not a super time to do this, but it will only be
harder in the future. Thiago, what do you think?
Tom
next prev parent reply other threads:[~2009-04-06 23:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 20:55 Tom Tromey
2009-04-03 15:16 ` Eli Zaretskii
2009-04-07 19:52 ` Tom Tromey
2009-04-07 21:45 ` Eli Zaretskii
2009-04-03 16:30 ` Daniel Jacobowitz
2009-04-06 23:26 ` Tom Tromey [this message]
2009-04-07 0:34 ` Thiago Jung Bauermann
2009-04-07 1:16 ` Daniel Jacobowitz
2009-04-07 2:03 ` Thiago Jung Bauermann
2009-04-07 2:27 ` Daniel Jacobowitz
2009-04-03 20:34 ` Thiago Jung Bauermann
2009-04-06 23:32 ` Tom Tromey
2009-04-08 18:26 ` Tom Tromey
2009-04-08 18:39 ` Tom Tromey
2009-04-08 19:23 ` Eli Zaretskii
2009-04-09 1:16 ` 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=m3eiw52wkx.fsf@fleche.redhat.com \
--to=tromey@redhat.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