From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>, Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/manual: Introduce locspecs
Date: Thu, 26 May 2022 09:41:31 -0400 [thread overview]
Message-ID: <196f6082-8f22-7a78-cd8e-817d706ad6b4@simark.ca> (raw)
In-Reply-To: <83a6b4pz04.fsf@gnu.org>
On 2022-05-26 02:51, Eli Zaretskii via Gdb-patches wrote:
>> Date: Wed, 25 May 2022 23:18:02 +0100
>> Cc: gdb-patches@sourceware.org
>> From: Pedro Alves <pedro@palves.net>
>>
>>> IIUC, Eli would like to have location reserved for a breakpoint giving multiple resulting
>>> locations.
>>
>> No, he was saying he would prefer "location" to be reserved for location specifications,
>> and to find a different name for breakpoint locations.
>
> Yes.
>
>> I don't see why would we even bother to consider renaming breakpoint
>> locations to something else.
>
> Because we want to use "location" for location specifications, and I
> would like us to avoid a confusing ambiguity.
FWIW, I also think that it's clearer to keep "location" for the
concrete, resolved locations in the program. "Location specification"
makes sense as a new term for what you pass to the "break" command (and
others).
Simon
next prev parent reply other threads:[~2022-05-26 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 19:31 Pedro Alves
2022-05-25 19:56 ` Eli Zaretskii
2022-05-25 20:05 ` Pedro Alves
2022-05-25 21:24 ` Philippe Waroquiers
2022-05-25 22:18 ` Pedro Alves
2022-05-26 6:51 ` Eli Zaretskii
2022-05-26 13:41 ` Simon Marchi [this message]
2022-05-26 12:56 ` Eli Zaretskii
2022-05-25 21:02 ` [PATCH v2] gdb/manual: Introduce location specs Pedro Alves
2022-05-26 6:50 ` Eli Zaretskii
2022-05-26 12:26 ` [PATCH v3] " Pedro Alves
2022-05-26 13:52 ` Eli Zaretskii
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=196f6082-8f22-7a78-cd8e-817d706ad6b4@simark.ca \
--to=simark@simark.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).