X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=jrvfsk
	L5qDVulRjFoDX6l1kqatGChBUC10JWuA4PFFB90vRecgVHBPox0bXREbPHCxeZUi
	pJYyWNpPkTh/imEAjblD1HklU8Sg86m+PydKCGG7vYS2etT5adVGuAEly8AdjUXO
	kWuc7gIQynx/xipqvTlntY4ePgAGOVUu+xu0E=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; s=default; bh=5wBTHW6TlmYf
	K3/qcAWIoCWfYOs=; b=GyT1iBkWzFgV2v7iuI9MGmIQdJtgseqH+66/DeMkOuhv
	UezLReOh0QNpFfeEoLxexJ0cSEJyBS5ytxG410nU03uEX1SC2GiUE5tcyAVCN8tQ
	DlGMf3uPxpg3A8D0lnC7ZFUsw23nmG/9KCyit9EHNNAtR/G/p4xGny73v0XrGqI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-8.6 required=5.0 tests=AWL,BAYES_50,KHOP_PGP_SIGNED,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,TW_EG autolearn=no version=3.3.1
Message-ID: <51ED6933.4050400@redhat.com>
Date: Mon, 22 Jul 2013 11:17:39 -0600
From: Eric Blake <eblake AT redhat DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: regex library fails git tests
References: <ksepor$cag$1 AT ger DOT gmane DOT org> <20130721193953 DOT GC2661 AT calimero DOT vinschen DOT de> <51ECA00D DOT 6030105 AT gmail DOT com> <20130722081200 DOT GE2661 AT calimero DOT vinschen DOT de>
In-Reply-To: <20130722081200.GE2661@calimero.vinschen.de>
OpenPGP: url=http://people.redhat.com/eblake/eblake.gpg
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TE5fTbxfkPeQsGpABH6IleJDUiJv162Fx"
X-Virus-Found: No

--TE5fTbxfkPeQsGpABH6IleJDUiJv162Fx
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 07/22/2013 02:12 AM, Corinna Vinschen wrote:

>>> However, please note that this behaviour, while being provided by glibc
>>> and now by Cygwin, is *not* standards-compliant.  In the narrow sense
>>> the characters beyond 0x7f are still invalid ASCII chars, and other
>>> functions working with wchar_t strings won't be as forgiving when using
>>> invalid input.
>>>

> After some sleep, I think I now understand why the glibc devs made
> regcomp to work this way.  This behaviour is backward compatible to non
> locale-aware applications.  In the "C" locale, a char is just some
> arbitrary byte between 0 and 255.  So this pattern always worked before
> in the "C locale, therefore it makes sense that it continues to work,
> even if it won't when using other locales/codesets.

By the way, there is currently a big debate going on in the Austin Group
(the people responsible for POSIX) on whether the "C" locale must be
8-bit clean (the way glibc behaves) or whether it was intended to allow
UTF-8 encoding by default (the way musl libc wants to behave); and
resolution of the debate will require input from the C standards
committee.  There may be some interesting fallout, no matter which
solution is finally reached.  http://austingroupbugs.net/view.php?id=3D663

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--TE5fTbxfkPeQsGpABH6IleJDUiJv162Fx
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJR7WkzAAoJEKeha0olJ0NqXJ0IAKBhuk6YKouOBwYOncZ/ZChj
OTI5G/S4UEwtp3jqwF/4X1rZr/engJGc7i+cylDyuvx8p5ZK9yN21tf1tjAwI6tt
RVRGUANjQTPvZOqDQQnNeNdsnPr92JmLiwLNQj2eRpH/CSL+RICf8ft8F7U1SGKC
A0xesnsV7vV0np7Dt0kK0j7ECXqNdDPGm+Ppwp07XeLeRSYJ5cMGwxO3HkO/H1TC
Sr/HjnkbtKg58S4RXy3tx77vkcispe/LWMpmOxj9mW9/xSaoRi5oDn/Vb00aWgv1
odViqYJ2ggL6qVmOatSP6AHCR3LBbmU1aCOjj3X8qtSfIUkv8a8OjMXpEGvPLms=
=fpO2
-----END PGP SIGNATURE-----

--TE5fTbxfkPeQsGpABH6IleJDUiJv162Fx--