mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Rich Felker <dalias@libc.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: Wed, 28 Oct 2020 11:05:58 +0100	[thread overview]
Message-ID: <1cf98be6a5be0cc841db58534767856f96baf69c.camel@klomp.org> (raw)
In-Reply-To: <20201027222515.GW534@brightrain.aerifal.cx>

Hi Rich,

On Tue, 2020-10-27 at 18:25 -0400, Rich Felker wrote:
> On Tue, Oct 27, 2020 at 11:19:11PM +0100, Mark Wielaard wrote:
> > On Tue, Oct 27, 2020 at 01:08:17PM -0400, Rich Felker wrote:
> > > 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.

No hostility intended at all. Please assume postive intend. I was just
pointing out what I believe are technical facts. That extended wildcard
patterns are well defined and supported in various context, how Posix
defines the fnmatch contract (which explicitly allows for error
handling) and that the Austin group has been willing to document and
specify GNU extensions to various standard functions.

I am really just trying to help some people who would like musl add
support for functionality elfutils relies on or find workarounds for
missing functionality. I realize extended wildcard support through
fnmatch is just one small part of that. There are certainly larger
issues to overcome. As far as I can see musl doesn't support argp,
obstack, fts, symbol versions and various on-stack string functions. So
there is certainly some work to do. But hopefully we can do that
without taking away any useful features from either project. I don't
believe anybody is trying to be hostile by trying to make these
projects work together. I do think it is useful to see if we can
standardize some of these glibc extensions projects are relying on.

Cheers,

Mark

  reply	other threads:[~2020-10-28 11:02 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
2020-10-28 10:05                   ` Mark Wielaard [this message]
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=1cf98be6a5be0cc841db58534767856f96baf69c.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).