public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15973] glibc should provide strnspn() and strncspn()
Date: Sun, 22 Sep 2013 05:20:00 -0000	[thread overview]
Message-ID: <bug-15973-131-7JjrFoBUSr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15973-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15973

Rich Felker <bugdal at aerifal dot cx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugdal at aerifal dot cx

--- Comment #2 from Rich Felker <bugdal at aerifal dot cx> ---
Why should more nonstandard functions with no precedent be added? At the very
least, a usage case for where it's important to have such a function and have a
highly optimized implementation in libc (as opposed to a trivial implementation
in the application that needs it) should be provided before this is even
considered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-09-22  5:20 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 [this message]
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
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=bug-15973-131-7JjrFoBUSr@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).