public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: philippe.waroquiers@skynet.be, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/manual: Introduce locspecs
Date: Thu, 26 May 2022 09:51:55 +0300	[thread overview]
Message-ID: <83a6b4pz04.fsf@gnu.org> (raw)
In-Reply-To: <ece793c3-98bc-213c-d165-14f926327f0b@palves.net> (message from Pedro Alves on Wed, 25 May 2022 23:18:02 +0100)

> 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.

  reply	other threads:[~2022-05-26  6:52 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 [this message]
2022-05-26 13:41           ` Simon Marchi
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=83a6b4pz04.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=philippe.waroquiers@skynet.be \
    /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).