From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Python pretty-printing [3/6]
Date: Tue, 07 Apr 2009 21:45:00 -0000 [thread overview]
Message-ID: <83bpr85ehv.fsf@gnu.org> (raw)
In-Reply-To: <m3tz50z1g7.fsf@fleche.redhat.com>
> Cc: gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Tue, 07 Apr 2009 13:52:08 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Tom> +@item bitpos
> Tom> +This attribute is not available for @code{static} fields. For
> Tom> +non-@code{static} fields, the value is the bit position of the field.
>
> Eli> What are "static fields"? Should that be explained here?
>
> A static field is a C++ (and Java, and probably others) concept. I
> don't think we should explain it, we can just refer to C++.
Here and elsewhere, I guess the best we can do now is for you to
mention the language(s) you know about, and someone else will have to
complete the information when it is available.
Thanks.
next prev parent reply other threads:[~2009-04-07 21:45 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 [this message]
2009-04-03 16:30 ` Daniel Jacobowitz
2009-04-06 23:26 ` Tom Tromey
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=83bpr85ehv.fsf@gnu.org \
--to=eliz@gnu.org \
--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