public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Ondřej Bílka" <neleai@seznam.cz>
To: fweimer at redhat dot com <sourceware-bugzilla@sourceware.org>
Cc: glibc-bugs@sourceware.org
Subject: Re: [Bug libc/15973] glibc should provide strnspn() and strncspn()
Date: Fri, 13 Jun 2014 13:04:00 -0000 [thread overview]
Message-ID: <20140613130424.GA12933@domone.podge> (raw)
In-Reply-To: <bug-15973-131-alQstKsrre@http.sourceware.org/bugzilla/>
On Fri, Jun 13, 2014 at 12:48:04PM +0000, fweimer at redhat dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=15973
>
> Florian Weimer <fweimer at redhat dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |fweimer at redhat dot com
>
> --- Comment #5 from Florian Weimer <fweimer at redhat dot com> ---
> The existing strspn function isn't even such a great model for an API. In most
> cases, it would be beneficial to pre-compile the pattern. I don't think it
> makes sense to add more interfaces with the same issue.
>
You could do caching on-line but it is not on my priority list.
next prev parent reply other threads:[~2014-06-13 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 17:19 [Bug libc/15973] New: " ooprala at redhat dot com
2013-09-21 17:19 ` [Bug libc/15973] " ooprala at redhat dot com
2013-09-21 17:27 ` [Bug libc/15973] New: " Ondřej Bílka
2013-09-21 17:28 ` [Bug libc/15973] " neleai at seznam dot cz
2013-09-22 5:20 ` bugdal at aerifal dot cx
2014-01-30 4:35 ` allachan at au1 dot ibm.com
2014-06-13 12:47 ` fweimer at redhat dot com
2014-06-13 12:48 ` fweimer at redhat dot com
2014-06-13 13:04 ` Ondřej Bílka [this message]
2014-06-13 13:05 ` neleai at seznam dot cz
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=20140613130424.GA12933@domone.podge \
--to=neleai@seznam.cz \
--cc=glibc-bugs@sourceware.org \
--cc=sourceware-bugzilla@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).