From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA][Python] Change gdb.Value.address from a method to an attribute.
Date: Sun, 29 Mar 2009 04:21:00 -0000 [thread overview]
Message-ID: <ur60hkoml.fsf@gnu.org> (raw)
In-Reply-To: <1238275138.8292.3.camel@localhost.localdomain>
> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: gdb-patches@sourceware.org
> Date: Sat, 28 Mar 2009 18:18:57 -0300
>
> +@defmethod Value address
> +If the @code{gdb.Value} object is addressable, this read-only attribute
> +holds a @code{gdb.Value} object representing the address. Otherwise,
> +this attribute holds @code{None}.
> +@end defmethod
The two uses of `gdb.Value' so close to one another and meaning two
different things might confuse the reader. Is it really important to
make the point that the address attribute is itself a `gdb.Value'? If
not, I'd suggest to rephrase:
If the @code{gdb.Value} object is addressable, this read-only
attribute holds its address.
Thanks.
next prev parent reply other threads:[~2009-03-29 3:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <orskllhfo3.fsf@oliva.athome.lsd.ic.unicamp.br>
[not found] ` <20090310125945.GA4376@caradoc.them.org>
[not found] ` <1236700079.11106.1.camel@localhost.localdomain>
[not found] ` <orzlftfhu1.fsf@oliva.athome.lsd.ic.unicamp.br>
[not found] ` <1236710732.11106.30.camel@localhost.localdomain>
[not found] ` <m3hc1rluz1.fsf@fleche.redhat.com>
2009-03-23 2:09 ` [RFC][Python] Re: any expression to tell whether a variable was optimized out? Thiago Jung Bauermann
2009-03-23 4:24 ` Eli Zaretskii
2009-03-26 21:21 ` Thiago Jung Bauermann
2009-03-23 17:47 ` Tom Tromey
2009-03-28 21:38 ` [RFA][Python] Change gdb.Value.address from a method to an attribute Thiago Jung Bauermann
2009-03-29 4:21 ` Eli Zaretskii [this message]
2009-03-29 18:12 ` Tom Tromey
2009-03-29 18:56 ` Eli Zaretskii
2009-03-29 21:22 ` Thiago Jung Bauermann
2009-03-29 15:42 ` 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=ur60hkoml.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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