From: Andrew Oakley <andrew@ado.is-a-geek.net>
To: gdb@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: Some Python ideas, looking for feedback
Date: Wed, 17 Aug 2011 19:35:00 -0000 [thread overview]
Message-ID: <20110817203525.6d789493@ado-gentoo> (raw)
In-Reply-To: <83sjozsuor.fsf@gnu.org>
On Wed, 17 Aug 2011 22:29:40 +0300
Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Wed, 17 Aug 2011 20:13:16 +0100
> > From: Andrew Oakley <andrew@ado.is-a-geek.net>
> > Cc: <gdb@sourceware.org>
> >
> > -position of the field.
> > +position of the field. For @code{enum} fields, the value is the
> > enumeration +member's integer representation.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> I don't understand this part. Can you elaborate, please? In
> particular, what does that `+' stand for?
Oops. That's a broken copy + paste into a email compose window. I
should have used git send-email so that didn't happen :(.
"Fixed" version:
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 6e7bf52..c82173b 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -21575,7 +21575,8 @@ Each field is an object, with some pre-defined
attributes: @item bitpos
This attribute is not available for @code{static} fields (as in
C@t{++} or Java). For non-@code{static} fields, the value is the bit
-position of the field.
+position of the field. For @code{enum} fields, the value is the
+enumeration member's integer representation.
@item name
The name of the field, or @code{None} for anonymous fields.
--
Andrew Oakley
next prev parent reply other threads:[~2011-08-17 19:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 11:04 Paul_Koning
2011-08-16 11:45 ` André Pönitz
2011-08-16 14:45 ` Paul_Koning
2011-08-17 18:37 ` Andrew Oakley
2011-08-17 19:13 ` Andrew Oakley
2011-08-17 19:29 ` Eli Zaretskii
2011-08-17 19:35 ` Andrew Oakley [this message]
2011-08-17 20:38 ` Eli Zaretskii
2011-08-17 20:52 ` Daniel Jacobowitz
2011-08-17 21:15 ` Paul_Koning
2011-08-19 14:14 ` Tom Tromey
[not found] ` <CAN9gPaFPhVYmfUO0sZeMUUy0X7x+hyUd8wDFJZXbe98RVvTLSw__33957.6404345737$1313614343$gmane$org@mail.gmail.com>
2011-08-19 14:14 ` Tom Tromey
2011-08-24 9:48 ` Andrew Oakley
2011-08-24 11:42 ` Phil Muldoon
2011-08-24 11:46 ` Andrew Oakley
2011-08-24 16:17 ` Phil Muldoon
[not found] ` <m3aaazavdq.fsf__47025.4836873666$1314186175$gmane$org@redhat.com>
2011-08-25 17:59 ` Tom Tromey
2011-08-24 11:39 ` Phil Muldoon
2011-08-30 20:09 ` 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=20110817203525.6d789493@ado-gentoo \
--to=andrew@ado.is-a-geek.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@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