From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jan Beulich <JBeulich@novell.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add stricmp
Date: Thu, 08 Sep 2005 17:04:49 +0100 [thread overview]
Message-ID: <1126195489.19834.39.camel@localhost.localdomain> (raw)
In-Reply-To: <432074B302000078000244A3@emea1-mh.id2.novell.com>
On Iau, 2005-09-08 at 17:28 +0200, Jan Beulich wrote:
> Then how am I supposed to do ASCII-only case-insensitive compares (i.e.
> reading config files)? And why is there a strnicmp? If this is not going
There is no such thing as "ascii" for case sensitivity. The case and
ordering rules are locale not symbol set based and they also depend
totally on the exact semantics of whatever legacy technology you are
interfacing with. I assume you mean "C locale, ascii character set",
which limits your debugger to speaking a subset of American English (no
café or naïve 8))
Any routine of that nature belongs in the user environment to which it
applies, and should be used with care, and preferably pushed to user
space or to a user app on the debug hosting box as kgdb does.
The only general, usable strnicmp safe for general kernel use would be a
full all singing all dancing UTF-8 symbol aware arbitary locale
implementation. And that we *definitely* do not want in kernel.
Alan
next prev parent reply other threads:[~2005-09-08 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 15:05 [PATCH] add stricmp Jan Beulich
2005-09-08 15:17 ` Christoph Hellwig
2005-09-08 15:28 ` Jan Beulich
2005-09-08 15:36 ` Christoph Hellwig
2005-09-08 16:04 ` Alan Cox [this message]
2005-09-08 15:45 ` Jan Beulich
2005-09-08 16:37 ` Alan Cox
2005-09-08 16:28 ` viro
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=1126195489.19834.39.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=JBeulich@novell.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.