From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sivachandra@google.com, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFC - doc] Add note about the possibility of symbols getting moved across blocks
Date: Fri, 27 Apr 2012 17:46:00 -0000 [thread overview]
Message-ID: <CADPb22Ric6paJziWuRJDp2tu_=R67pTgdawoPPtCkqm3OYD9kA@mail.gmail.com> (raw)
In-Reply-To: <83lilhgk1o.fsf@gnu.org>
On Fri, Apr 27, 2012 at 10:29 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 27 Apr 2012 09:49:35 -0700
>> From: Doug Evans <dje@google.com>
>> Cc: tromey@redhat.com, gdb-patches@sourceware.org
>>
>> > A @code{gdb.Block} is iterable. The iterator returns the symbols
>> > (@pxref{Symbols In Python}) local to the block. Python programs
>> > should not assume that a specific block object will always contain a
>> > given symbol, since changes in @value{GDBN} features and
>> > infrastructure may cause symbols move across blocks in a symbol
>> > table.
>>
>> I think that's close enough.
>>
>> s/symbols move/symbols to move/ ?
>
> I think omitting "to" makes it more correct English.
Really? Huh.
It's not important enough, so whichever "works for me".
next prev parent reply other threads:[~2012-04-27 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 8:13 Siva Chandra
2012-04-25 9:02 ` Eli Zaretskii
2012-04-25 20:02 ` Tom Tromey
2012-04-25 21:02 ` Eli Zaretskii
2012-04-26 14:04 ` Tom Tromey
2012-04-26 14:17 ` Eli Zaretskii
2012-04-27 13:15 ` Siva Chandra
2012-04-27 15:38 ` Eli Zaretskii
2012-04-27 16:59 ` Doug Evans
2012-04-27 17:33 ` Eli Zaretskii
2012-04-27 17:46 ` Doug Evans [this message]
2012-04-27 19:42 ` Siva Chandra
2012-04-28 7:15 ` Eli Zaretskii
2012-04-30 19:20 ` Siva Chandra
2012-05-02 17:32 ` Siva Chandra
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='CADPb22Ric6paJziWuRJDp2tu_=R67pTgdawoPPtCkqm3OYD9kA@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.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