From: ludo@gnu.org (Ludovic Courtès)
To: Eli Zaretskii <eliz@gnu.org>
Cc: Doug Evans <xdje42@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH, doc RFA] Split create-breakpoint! into make-breakpoint, register-breakpoint!
Date: Wed, 04 Jun 2014 08:29:00 -0000 [thread overview]
Message-ID: <87y4xdf57p.fsf@gnu.org> (raw)
In-Reply-To: <83fvjl889b.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 04 Jun 2014 10:05:20 +0300")
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’.
next prev parent reply other threads:[~2014-06-04 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 4:54 Doug Evans
2014-06-04 7:05 ` Eli Zaretskii
2014-06-04 8:29 ` Ludovic Courtès [this message]
2014-06-04 9:27 ` Eli Zaretskii
2014-06-04 13:47 ` Ludovic Courtès
2014-06-04 8:30 ` Ludovic Courtès
2014-06-05 2:58 ` Doug Evans
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=87y4xdf57p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.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