This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH, doc RFA] Split create-breakpoint! into make-breakpoint, register-breakpoint!
- From: ludo at gnu dot org (Ludovic CourtÃs)
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Doug Evans <xdje42 at gmail dot com>, gdb-patches at sourceware dot org
- Date: Wed, 04 Jun 2014 10:29:14 +0200
- Subject: Re: [PATCH, doc RFA] Split create-breakpoint! into make-breakpoint, register-breakpoint!
- Authentication-results: sourceware.org; auth=none
- References: <m3egz5cm1v dot fsf at sspiff dot org> <83fvjl889b dot fsf at gnu dot org>
Eli Zaretskii <eliz@gnu.org> skribis:
>> From: Doug Evans <xdje42@gmail.com>
>> Date: Tue, 03 Jun 2014 21:53:48 -0700
>>
>> In keeping with the splitting of object creation and registration into
>> two separate pieces, this does the same for breakpoints.
>> "Consistency Is Good".
>>
>> There hasn't been an FSF release of gdb+guile yet so I think it's ok
>> to remove create-breakpoint! here.
>
> OK for the documentation part, but is delete-breakpoint a better name
> than breakpoint-delete?.
I prefer âdelete-breakpoint!â.
> A question: how does one discard breakpoint objects so that they no
> longer exist? It seems that breakpoint-delete! only "deregisters" the
> breakpoint, but there's no way to undo the effect of the
> create-breakpoint procedure.
They just get garbage collected eventually.
Ludoâ.