From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch][doc] PR python/10781
Date: Fri, 16 Oct 2009 18:44:00 -0000 [thread overview]
Message-ID: <8363afi3hf.fsf@gnu.org> (raw)
In-Reply-To: <m37huvjjqy.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: Phil Muldoon <pmuldoon@redhat.com>, gdb-patches@sourceware.org
> Date: Fri, 16 Oct 2009 12:07:01 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> >> +Cast the @code{gdb.Value} to the type represented by @var{type}, and
> Eli> ^^^
> Eli> Please remove this "the".
>
> Removing the "the" makes this read strangely.
> gdb.Value is a class, the "the" indicates that it is an instance which is
> cast.
Then how about "Cast an instance of @code{gdb.Value} ..."?
> >> +return a new @code{gdb.Value}. @var{type} must be a @code{gdb.Type}
> >> +object.
>
> Eli> If TYPE is an object, then it probably isn't a good idea to call it
> Eli> TYPE. Why not OBJECT?
>
> I think it is generally preferable to name parameters according to their
> use.
No, they should be named according to their essence, i.e. what they
are.
> "object" is not specific enough.
I'm open to other suggestions.
> Eli> Anyway, what does it mean "the type represented by TYPE"? How can a
> Eli> type be "represented"? Did you perhaps mean "the type of TYPE"?
>
> gdb.Type represents a type in the inferior.
Sorry, I still don't understand.
next prev parent reply other threads:[~2009-10-16 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 7:35 Phil Muldoon
2009-10-16 7:46 ` Eli Zaretskii
2009-10-16 18:07 ` Tom Tromey
2009-10-16 18:44 ` Eli Zaretskii [this message]
2009-10-16 18:49 ` Tom Tromey
2009-10-16 19:09 ` Eli Zaretskii
2009-10-19 17:50 ` Tom Tromey
2009-10-27 15:52 ` Phil Muldoon
2009-10-27 16:01 ` Phil Muldoon
2009-10-27 18:43 ` Eli Zaretskii
2009-10-27 20:58 ` Phil Muldoon
2009-10-27 21:14 ` Eli Zaretskii
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=8363afi3hf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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