Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Siva Chandra <sivachandra@google.com>
Cc: dje@google.com, gdb-patches@sourceware.org
Subject: Re: [RFC - Python Scripting] Add 'end' attribute to gdb.Symtab_and_line
Date: Tue, 12 Jun 2012 19:43:00 -0000	[thread overview]
Message-ID: <83ehpkz574.fsf@gnu.org> (raw)
In-Reply-To: <CAGyQ6gwDhacRNuCxvsWRnt7tKDJ2_0iyryw+hdL5rsq+h3MaAA@mail.gmail.com>

> Date: Wed, 13 Jun 2012 00:10:39 +0530
> From: Siva Chandra <sivachandra@google.com>
> Cc: gdb-patches@sourceware.org
> 
> +  ** gdb.Symtab_and_line has new attribute 'end_pc' which holds the end
> +     address of the program counter address range for the current source
> +     line.

Perhaps this minor rewording is better:

  gdb.Symtab_and_line has a new attribute 'end_pc' which holds the end
  of the address range occupied by code for the current source line.

> +@defvar Symtab_and_line.end_pc
> +Indicates the end address of the program counter address range for
> +the current source line.  This attribute is not writable.
> +@end defvar

Can you reword this so as not to use "address" twice in the same
sentence, like I did for NEWS?

Thanks.


  reply	other threads:[~2012-06-12 19:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  8:40 Siva Chandra
2012-05-21 16:27 ` Eli Zaretskii
2012-06-01 19:57 ` Siva Chandra
2012-06-11  9:17 ` Siva Chandra
2012-06-11 21:22 ` Doug Evans
2012-06-12 18:41   ` Siva Chandra
2012-06-12 19:43     ` Eli Zaretskii [this message]
2012-06-13  7:24       ` Siva Chandra
2012-06-13 15:15         ` Eli Zaretskii
2012-06-13 13:29     ` Siva Chandra
2012-06-13 17:08       ` Doug Evans
2012-06-13 18:15         ` Siva Chandra
2012-06-22  9:21           ` Siva Chandra
2012-06-22 17:12           ` Tom Tromey
2012-06-22 21:12             ` Doug Evans
2012-06-24 17:03             ` Siva Chandra
2012-06-26 22:12               ` Doug Evans
2012-06-27  0:23                 ` Siva Chandra
2012-06-22 17:10 ` Tom Tromey
2012-06-22 18:43   ` 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=83ehpkz574.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sivachandra@google.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