This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Handle multiple breakpoint hits in Python interface
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.
>