From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Python pretty-printing [3/6]
Date: Tue, 07 Apr 2009 00:34:00 -0000 [thread overview]
Message-ID: <1239064468.8871.42.camel@localhost.localdomain> (raw)
In-Reply-To: <m3eiw52wkx.fsf@fleche.redhat.com>
El lun, 06-04-2009 a las 17:26 -0600, Tom Tromey escribió:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
> 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?
I prefer to have a separate lookup routine. A gdb.lookup_type function
would be more consistent with the little API direction we already have
than a Type.lookup static method (I remember we discussed module
functions vs static methods in the past, I don't remember the outcome
though). Well, you asked what I thought. :-)
I don't want to inflict any pain on you, though. I don't feel strongly
about these choices. I wouldn't mind if you preferred to keep it like
this. Or if you preferred to implement Type.lookup.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-04-07 0:34 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
2009-04-07 0:34 ` Thiago Jung Bauermann [this message]
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=1239064468.8871.42.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--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