From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: roirand@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFA v3] enable/disable sub breakpoint range
Date: Tue, 03 Oct 2017 18:32:00 -0000 [thread overview]
Message-ID: <83tvzgytdx.fsf@gnu.org> (raw)
In-Reply-To: <81b6ce9e-1ee0-1c60-81d4-869f7a9d6b5e@redhat.com> (message from Pedro Alves on Tue, 3 Oct 2017 18:15:39 +0100)
> Cc: roirand@adacore.com, gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 3 Oct 2017 18:15:39 +0100
>
> > Wouldn't it be better to use 1.3-1.5 for the subranges, and then we
> > could still say 1.3-5 to mean all the breakpoints between 1.3 and 5?
>
> IMO, I'd rather not treat treat locations as decimals.
Fair enough. Let me just say that, as a user, the notion that 1.3-5
actually 'expands" into "1.3 1.4 1.5" is extremely surprising, as
that's not what I'm used to in other similar situations. But maybe
I'm just the odd one out.
next prev parent reply other threads:[~2017-10-03 18:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 10:26 Xavier Roirand
2017-10-03 14:50 ` Eli Zaretskii
2017-10-03 16:02 ` Pedro Alves
2017-10-03 16:05 ` Pedro Alves
2017-10-03 16:06 ` Xavier Roirand
2017-10-03 16:34 ` Eli Zaretskii
2017-10-03 16:40 ` Pedro Alves
2017-10-03 17:00 ` Eli Zaretskii
2017-10-03 17:15 ` Pedro Alves
2017-10-03 18:32 ` Eli Zaretskii [this message]
2017-10-06 8:54 ` Xavier Roirand
2017-10-16 22:21 ` Philippe Waroquiers
2017-10-20 12:17 ` Xavier Roirand
2017-10-20 14:41 ` Pedro Alves
2017-10-20 14:58 ` Pedro Alves
[not found] ` <c1310ac2-b958-f0b6-aabd-5f14f8524b79@adacore.com>
2017-10-23 10:25 ` [RFA v4] " Pedro Alves
2017-10-23 11:07 ` Xavier Roirand
2017-10-26 13:11 ` Pedro Alves
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=83tvzgytdx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=roirand@adacore.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