From: Stan Shebs <stan@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stan Shebs <stan@codesourcery.com>, gdb@sourceware.org
Subject: Re: [RFC] "actionpoints"?
Date: Mon, 18 Jan 2010 16:51:00 -0000 [thread overview]
Message-ID: <4B549177.4050703@codesourcery.com> (raw)
In-Reply-To: <83iqb2cwhe.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Fri, 15 Jan 2010 16:22:35 -0800
>> From: Stan Shebs <stan@codesourcery.com>
>>
>> It turns out there is a generic term available - "actionpoint". It
>> originally comes from TotalView I think, and was adopted into the HPD
>> (high performance debugger) spec back in the 90s.
>>
>> A plus is that the term is sufficiently vague that it is sensible for
>> watchpoints, catchpoints, tracepoints, breakpoints, and the rest of the
>> menagerie, including future ideas we haven't thought of yet. A minus is
>> that it means having to teach an unfamiliar term to users, and it
>> entails a certain amount of hacking up the manual.
>>
>
> Not only the manual, but also some commands, such as "info break".
> They will have to be renamed.
>
I don't think that one can be changed, it's just too heavily used in its
current form. That doesn't preclude adding new synonyms, and maybe
something like "info just-breakpoints" if anyone really wants that.
Stan
next prev parent reply other threads:[~2010-01-18 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 0:22 Stan Shebs
2010-01-16 7:57 ` Eli Zaretskii
2010-01-18 16:51 ` Stan Shebs [this message]
2010-01-18 18:08 ` Eli Zaretskii
2010-01-16 13:51 ` Frank Ch. Eigler
2010-01-18 17:09 ` Stan Shebs
2010-01-18 6:44 ` Joel Brobecker
2010-01-18 17:54 ` Eli Zaretskii
2010-01-18 18:18 ` Joel Brobecker
2010-01-18 18:53 ` Stan Shebs
2010-01-18 19:08 ` Pedro Alves
2010-01-18 18:44 ` Stan Shebs
2010-01-18 19:04 ` Pedro Alves
2010-01-21 21:24 ` Daniel Jacobowitz
2010-01-18 19:35 ` Frank Ch. Eigler
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=4B549177.4050703@codesourcery.com \
--to=stan@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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