From: Mark Wielaard <mark@klomp.org>
To: Florian Weimer <fweimer@redhat.com>, Rich Felker <dalias@libc.org>
Cc: elfutils-devel@sourceware.org, musl@lists.openwall.com,
"Érico Rolim" <erico.erc@gmail.com>, "Max Rees" <maxcrees@me.com>
Subject: Re: [musl] Re: [QUESTION] Which fnmatch() functionality does elfutils depend on?
Date: Tue, 27 Oct 2020 16:04:44 +0100 [thread overview]
Message-ID: <69fc8640a4ec2d22fdf3e6526c5f0040e42b524a.camel@klomp.org> (raw)
In-Reply-To: <87wnzc81r9.fsf@oldenburg2.str.redhat.com>
On Tue, 2020-10-27 at 10:19 +0100, Florian Weimer via Elfutils-devel
wrote:
> * Rich Felker:
>
> > As I stated in my other reply, I'm opposed to that because it does not
> > admit implementation with the same (very desirable) big-O properties,
> > and the "extmatch" syntax is not widely known or widely used.
>
> The syntax comes from ksh and is used in shell scripts. (bash requires
> the extglob option to enable it, which makes it easy to search for
> instances.)
Right, it is also adopted by zsh and some other shells. The big-O
properties don't really matter in this case because fnmatch is used on
small input strings like file names (or in this case section names).
Cheers,
Mark
next prev parent reply other threads:[~2020-10-27 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <723b967389be88475206c5afc280c3be02ab677c.camel@klomp.org>
2020-10-26 17:28 ` Érico Nogueira
2020-10-26 17:54 ` Max Rees
2020-10-26 22:32 ` Mark Wielaard
2020-10-26 23:25 ` Rich Felker
2020-10-27 9:19 ` Florian Weimer
2020-10-27 15:04 ` Mark Wielaard [this message]
2020-10-27 17:08 ` Rich Felker
2020-10-27 22:19 ` Mark Wielaard
2020-10-27 22:25 ` Rich Felker
2020-10-28 10:05 ` Mark Wielaard
2020-10-28 14:03 ` Rich Felker
2020-10-26 19:55 ` Rich Felker
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=69fc8640a4ec2d22fdf3e6526c5f0040e42b524a.camel@klomp.org \
--to=mark@klomp.org \
--cc=dalias@libc.org \
--cc=elfutils-devel@sourceware.org \
--cc=erico.erc@gmail.com \
--cc=fweimer@redhat.com \
--cc=maxcrees@me.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).