From: Rich Felker <dalias@libc.org>
To: Mark Wielaard <mark@klomp.org>
Cc: "Florian Weimer" <fweimer@redhat.com>,
musl@lists.openwall.com, "Érico Rolim" <erico.erc@gmail.com>,
elfutils-devel@sourceware.org, "Max Rees" <maxcrees@me.com>
Subject: Re: [musl] Re: [QUESTION] Which fnmatch() functionality does elfutils depend on?
Date: Tue, 27 Oct 2020 18:25:15 -0400 [thread overview]
Message-ID: <20201027222515.GW534@brightrain.aerifal.cx> (raw)
In-Reply-To: <20201027221911.GB2691@wildebeest.org>
On Tue, Oct 27, 2020 at 11:19:11PM +0100, Mark Wielaard wrote:
> Hi Rich,
>
> On Tue, Oct 27, 2020 at 01:08:17PM -0400, Rich Felker wrote:
> > On Tue, Oct 27, 2020 at 04:04:44PM +0100, Mark Wielaard wrote:
> > > 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).
> >
> > They do because they're also in space, unless you want
> > exponential-time which is huge even on small inputs, and greater than
> > O(1) space requirement means the interface can't satisfy its contract
> > to return a conclusive result for valid inputs.
>
> But that isn't the contract if fnmatch. fnmatch returns 0 for a match
> and non-zero for either a non-match or some error. So if your
> algorithm hits some error case, like out of memory, returning a
> non-zero result is fine.
>
> I believe the extended wildcard pattern are widely supported and
> useful. If you don't want to implement them because they aren't in any
> standardized enough yet we can ask the Austin Group to add them to
> fnmatch. They have adopted other GNU flags for fnmatch in the past.
And I can ask them not to. Your hostility is really unwelcome here.
Rich
next prev parent reply other threads:[~2020-10-27 22:25 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
2020-10-27 17:08 ` Rich Felker
2020-10-27 22:19 ` Mark Wielaard
2020-10-27 22:25 ` Rich Felker [this message]
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=20201027222515.GW534@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=elfutils-devel@sourceware.org \
--cc=erico.erc@gmail.com \
--cc=fweimer@redhat.com \
--cc=mark@klomp.org \
--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).