From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Siva Chandra <sivachandra@google.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [Patch] PR python/15464 and python/16113
Date: Wed, 15 Jan 2014 12:46:00 -0000 [thread overview]
Message-ID: <20140115124617.GK4762@adacore.com> (raw)
In-Reply-To: <87ha96y5wa.fsf@fleche.redhat.com>
> Siva> Forgot to ask, should this go into 7.7 branch as well? The first patch
> Siva> is in 7.7.
>
> It seems reasonable to me, given that the feature is a bit incomplete
> without this patch, but I'd rather defer to Joel for 7.7 decisions.
I have no objection in this case, so I'll defer to Tom in return :).
The patch is fairly large, in areas where I don't necessarily understand
all the repercutions. Hence it is good that Tom's OK with it - so
go head, and push to 7.7.
By the way, I happened to notice a couple of style violations which
I just fixed:
+ {
+ const char *field_name = TYPE_FIELD_NAME (type, field);
+ if (field_name[0] != '\0')
+ {
Empty line after local declaration.
+ if (ftype == NULL)
+ {
+ PyErr_SetString (PyExc_TypeError,
+ _("'type' attribute of gdb.Field object is not a "
+ "gdb.Type object."));
+ }
No need for the curly braces.
They are obviously not important for the gdb-7.7 branch, unless you
think there is a chance we might touch this code again in the near
future, and would want to backport to 7.7. In that case, cherry-picking
those two commits on the gdb-7.7 branch would help avoiding patching
conflicts...
--
Joel
next prev parent reply other threads:[~2014-01-15 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 22:38 Siva Chandra
2013-12-30 14:27 ` Siva Chandra
2014-01-06 20:50 ` Tom Tromey
2014-01-07 14:28 ` Siva Chandra
2014-01-13 21:12 ` Tom Tromey
2014-01-14 1:51 ` Siva Chandra
2014-01-14 14:48 ` Siva Chandra
2014-01-14 14:50 ` Tom Tromey
2014-01-15 12:46 ` Joel Brobecker [this message]
2014-01-15 13:19 ` Siva Chandra
2014-01-06 20:36 ` 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=20140115124617.GK4762@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.com \
--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