From: Kevin Pouget <kevin.pouget@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle multiple breakpoint hits in Python interface
Date: Mon, 23 May 2011 11:01:00 -0000 [thread overview]
Message-ID: <BANLkTi=AkFSDK3UZjGhfp0S+i3nVaxL03Q@mail.gmail.com> (raw)
In-Reply-To: <E1QOSjM-0002XU-Fl@fencepost.gnu.org>
hello,
> ...this. What is that phrase in parens for? Can it be removed?
do you mean the phrase or the parens?
The reason why I added this comment is that, to my eyes,
BreakpointEvent.breakpoint don't make sense anymore because it is
incomplete and inaccurate, but it's kept in order not to break the
backward compatibility. Maybe 'deprecated' would be a better wording ?
cordially,
Kevin
On Mon, May 23, 2011 at 6:51 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Kevin Pouget <kevin.pouget@gmail.com>
>> Date: Mon, 23 May 2011 05:38:54 -0400
>> Cc: gdb-patches@sourceware.org
>>
>> 2011-04-22 Kevin Pouget <kevin.pouget@st.com>
>>
>> Handle multiple breakpoint hits in Python interface:
>> * gdb.texinfo (Events In Python): Indicate that multiple breakpoint
>> may have been hit and rename the variable to breakpoints.
>
> This part is OK, except...
>
>> +@defivar BreakpointEvent breakpoint
>> +A reference to the first breakpoint that was hit of type @code{gdb.Breakpoint}.
>> +(Legacy support.)
> ^^^^^^^^^^^^^^^^^
> ...this. What is that phrase in parens for? Can it be removed?
>
> Thanks.
>
next prev parent reply other threads:[~2011-05-23 11:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTik-ffBpfx4BALF5+Y0xSx_NnaCs7g@mail.gmail.com>
2011-04-22 9:34 ` Kevin Pouget
2011-05-19 18:34 ` Tom Tromey
2011-05-23 9:39 ` Kevin Pouget
2011-05-23 10:51 ` Eli Zaretskii
2011-05-23 11:01 ` Kevin Pouget [this message]
2011-05-23 11:59 ` Eli Zaretskii
2011-05-27 20:09 ` Tom Tromey
2011-05-30 7:37 ` Kevin Pouget
2011-05-30 7:49 ` Eli Zaretskii
2011-05-30 10:53 ` Kevin Pouget
2011-08-31 17:49 ` Tom Tromey
2011-09-01 8:36 ` Kevin Pouget
2011-09-01 8:52 ` Kevin Pouget
2011-09-01 10:08 ` Pedro Alves
2011-09-01 10:18 ` Eli Zaretskii
2011-09-01 11:41 ` Kevin Pouget
2011-09-01 15:39 ` Pedro Alves
2011-09-01 20:53 ` Eli Zaretskii
2011-09-15 12:34 ` Kevin Pouget
2011-09-16 7:55 ` [commit] gdb.python/py-evthreads.exp regression [Re: [PATCH] Handle multiple breakpoint hits in Python interface] Jan Kratochvil
2011-09-16 9:12 ` Kevin Pouget
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='BANLkTi=AkFSDK3UZjGhfp0S+i3nVaxL03Q@mail.gmail.com' \
--to=kevin.pouget@gmail.com \
--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