Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
MIME-Version: 1.0
In-Reply-To: <56548B3E.7080004@aldan.algebra.com>
References: <FD60B807-973B-4FFD-B32F-E7608A6CD374@jaguNET.com>
	<CAKQ1sVPtxJRfyeS5LBJ7FsYJW5=36p9qp6FuE3hPFi19+WR9Eg@mail.gmail.com>
	<301856DC-1727-4158-96B0-8233D2E01CA9@jaguNET.com>
	<5653732E.9030401@wanadoo.fr>
	<6C408DFD-A50D-4DDF-8090-6488CA9C06C4@jaguNET.com>
	<CACsi253ZgU4waaAiEQm8E6X0gVoEfPw=JdQQ5t7KMNcma5EERA@mail.gmail.com>
	<56548B3E.7080004@aldan.algebra.com>
Date: Tue, 24 Nov 2015 10:53:28 -0600
Message-ID: 
 <CACsi251cmdO_wbjjvDeBc55iZEHKOoNQVvKcnqSxbB6V1W8JKg@mail.gmail.com>
Subject: Re: strncasecmp
From: William A Rowe Jr <wrowe@rowe-clan.net>
To: httpd <dev@httpd.apache.org>
Content-Type: multipart/alternative; boundary=001a113f93be5a0c7105254c2ef6

--001a113f93be5a0c7105254c2ef6
Content-Type: text/plain; charset=UTF-8

On Tue, Nov 24, 2015 at 10:07 AM, Mikhail T. <mi+thun@aldan.algebra.com>
wrote:

> On 24.11.2015 10:08, William A Rowe Jr wrote:
>
> As long as this function is promoted for fast ASCII-specific token
> recognition and has no other unexpected equalities, it serves a useful
> purpose.
>
> Because of this, I'd suggest renaming it to something, that emphasizes it
> being ASCII-only.
>

Strictly speaking, you are referring to US-ASCII, while the actual function
including
the EBCDIC build follows LC_CTYPE/LC_COLLATE C or POSIX (equivalent names
for the same thing) and is honoring LC_COLLATE of the US-ASCII ordering.

apr_strcasecmp_lcposix or apr_strcasecmp_lcc might be a usable name.  Other
suggestions?  I was leaning toward apr_strcasecmp_token since that is a
pretty
well recognized RFC term and usually refers to the ASCII set.  For HTTPbis,
token
is defined at http://tools.ietf.org/html/rfc7230#section-3.2.6

--001a113f93be5a0c7105254c2ef6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Nov 24, 2015 at 10:07 AM, Mikhail T. <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:mi+thun@aldan.algebra.com" target=3D"_blank">mi+thun@aldan.algebra.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D"">
    <div>On 24.11.2015 10:08, William A Rowe Jr
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div>As long as this function is promoted for fast ASCII-specific
        token</div>
      <div>recognition and has no other unexpected equalities, it serves
        a useful</div>
      <div>purpose.</div>
    </blockquote></span>
    Because of this, I&#39;d suggest renaming it to something, that
    emphasizes it being ASCII-only.</div></blockquote><div><br></div><div>S=
trictly speaking, you are referring to US-ASCII, while the actual function =
including</div><div>the EBCDIC build follows LC_CTYPE/LC_COLLATE C or POSIX=
 (equivalent names</div><div>for the same thing) and is honoring LC_COLLATE=
 of the US-ASCII ordering.</div><div><br></div><div>apr_strcasecmp_lcposix =
or=C2=A0apr_strcasecmp_lcc might be a usable name.=C2=A0 Other</div><div>su=
ggestions?=C2=A0 I was leaning toward apr_strcasecmp_token since that is a =
pretty</div><div>well recognized RFC term and usually refers to the ASCII s=
et.=C2=A0 For HTTPbis, token</div><div>is defined at=C2=A0<a href=3D"http:/=
/tools.ietf.org/html/rfc7230#section-3.2.6">http://tools.ietf.org/html/rfc7=
230#section-3.2.6</a></div><div><br></div><div><br></div><div><br></div><di=
v><br></div><div><br></div><div><br></div></div></div></div>

--001a113f93be5a0c7105254c2ef6--