From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [PATCH v3 2/2] compile: Add 'set compile-gcc'
Date: Mon, 27 Apr 2015 19:55:00 -0000 [thread overview]
Message-ID: <553E8CE0.40903@redhat.com> (raw)
In-Reply-To: <20150427175445.GA12679@host1.jankratochvil.net>
On 04/27/2015 06:54 PM, Jan Kratochvil wrote:
> On Mon, 27 Apr 2015 17:47:42 +0200, Pedro Alves wrote:
>> IIUC, gdb will always apply the same search as when this is set
>> empty? That is, the user can also set this to a regex. So it seems to me
>> that the documentation (manual and help) doesn't match the implementation?
>
> That it can be also a regex is an API bug because I wanted to make a minimal
> API change. Rather than officially documenting such bug I find then better to
> rather make a proper complex change to the API. Given that you requested an
> API rework anyway I will try to post the new API even with this change.
This overload had given me lots of pause, and trying to think it through
(it wasn't clear what the intention was), it seemed to me that it kind of made at
least some sense to allow specifying a different regex, but details of the search
algorithms are foggy to me. It probably really doesn't make sense to overload.
Given we now clearly understand how to add new methods and it isn't that complex,
and we're already bumping the API, yes, let's please avoid an overload hack
when we don't need it, avoiding such confusions.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-04-27 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 20:34 [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename Jan Kratochvil
2015-04-23 20:34 ` [PATCH v2 2/2] compile: Add 'set compile-gcc' Jan Kratochvil
2015-04-23 21:08 ` [PATCH v3 " Jan Kratochvil
2015-04-27 15:47 ` Pedro Alves
2015-04-27 17:54 ` Jan Kratochvil
2015-04-27 19:55 ` Pedro Alves [this message]
2015-04-27 15:31 ` [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename Pedro Alves
2015-04-27 16:48 ` Jan Kratochvil
2015-04-27 17:19 ` Pedro Alves
2015-04-27 17:52 ` Jan Kratochvil
2015-04-27 19:17 ` Pedro Alves
2015-04-27 20:44 ` Jan Kratochvil
2015-04-27 20:50 ` Jan Kratochvil
2015-04-27 21:49 ` Phil Muldoon
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=553E8CE0.40903@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@redhat.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