Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] New python module gdb.types
Date: Wed, 06 Oct 2010 23:44:00 -0000	[thread overview]
Message-ID: <AANLkTimGHuWxdo4LCBF6LnSFodq0hSc+NSXu6yT-79On@mail.gmail.com> (raw)
In-Reply-To: <m3d3rn2cpo.fsf@fleche.redhat.com>

On Wed, Oct 6, 2010 at 3:11 PM, Tom Tromey <tromey@redhat.com> wrote:
> I wouldn't mind if has_field were made a method on Type, but of course
> that can be done at any time.

It could, but there are design issues.
E.g., the has_field function calls get_basic_type and traverses base
types (instead of treating base types as a field which is what the
current gdb.Type API does.  It's an internal implementation detail of
gdb that got exposed.  Maybe it's reasonable to keep, I don't know).
Whether Type.has_field should do that ... I'm not sure.
It felt safer to see what works as a separate function before
expanding gdb.Type.

> I think the documentation would be a little improved if the gdb.Type
> documentation had an xref to the new module's documentation.

Thanks.


  reply	other threads:[~2010-10-06 23:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 20:49 Doug Evans
2010-10-06 21:04 ` Eli Zaretskii
2010-10-08 22:19   ` Doug Evans
2010-10-08 22:21     ` Doug Evans
2010-10-09  9:14     ` Eli Zaretskii
2010-10-13 18:42       ` Doug Evans
2010-10-13 18:49         ` Eli Zaretskii
2010-10-06 21:12 ` Joel Brobecker
2010-10-06 22:12 ` Tom Tromey
2010-10-06 23:44   ` Doug Evans [this message]
2010-10-08 23:08 ` 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=AANLkTimGHuWxdo4LCBF6LnSFodq0hSc+NSXu6yT-79On@mail.gmail.com \
    --to=dje@google.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