From: Paul Koning <paulkoning@comcast.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [RFA] Python: PR/13327: expose laziness to Python
Date: Tue, 25 Oct 2011 18:54:00 -0000 [thread overview]
Message-ID: <B107C20A-8E40-46D2-AA71-1090D09F0809@comcast.net> (raw)
In-Reply-To: <83fwihc4xw.fsf@gnu.org>
On Oct 25, 2011, at 2:16 PM, Eli Zaretskii wrote:
>> From: Paul Koning <paulkoning@comcast.net>
>> Date: Tue, 25 Oct 2011 13:38:20 -0400
>> Cc: Tom Tromey <tromey@redhat.com>
>>
>> The documentation briefly touches on how lazy fetching works in the discussion of the is_lazy attribute, but it doesn't more fully discuss it as a topic of its own. I could try to do so, in the introductory material for gdb.Value. Should I do that?
>
> No, I think what you wrote is good enough.
>
>> Ok to commit?
>
> A few comments to the documentation part:
>
>> +@defvar Value.is_lazy
>> +This read-only boolean attribute is true if the value has not yet
>
> "The attribute is true" sounds weird, doesn't it? How about
>
> The value of this read-only attribute is @code{True} if @code{Value}
> has not yet been fetched ...
What I wrote originally was copied from is_optimized_out. But I like your wording better. I made it "...if this @code{gdb.Value} has not yet..." which is the wording used in the other attributes directly above this one.
> ...
> Okay with these changes.
Thanks. Committed that way.
paul
prev parent reply other threads:[~2011-10-25 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 17:43 Paul Koning
2011-10-25 18:24 ` Eli Zaretskii
2011-10-25 18:54 ` Paul Koning [this message]
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=B107C20A-8E40-46D2-AA71-1090D09F0809@comcast.net \
--to=paulkoning@comcast.net \
--cc=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