Date: Mon, 4 Aug 2003 18:43:58 +0400 From: Andrey Chernov <ache@nagual.pp.ru> To: Ruslan Ermilov <ru@freebsd.org> Cc: current@freebsd.org Subject: Re: buildworld broken after installworld Message-ID: <20030804144358.GA81091@nagual.pp.ru> In-Reply-To: <20030804141858.GB60105@sunbay.com> References: <20030804195135.0562a9a2.yosimoto@waishi.jp> <20030804114723.GB39384@sunbay.com> <20030804223833.6c9a6718.yosimoto@waishi.jp> <20030804134636.GA39138@nagual.pp.ru> <20030804135713.GA39289@nagual.pp.ru> <20030804140332.GA39367@nagual.pp.ru> <20030804141858.GB60105@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 04, 2003 at 17:18:58 +0300, Ruslan Ermilov wrote: > : The characters or collating elements in the > : range shall be placed in the array in ascending > : collation sequence. If the second endpoint > : precedes the starting endpoint in the collation > : sequence, it is unspecified whether the range Do you read first part about collation sequence? We just implement that, i.e. collation sequence for all, including non-POSIX locale which allowed as unspecified. > : of collating elements is empty, or this construct > : is treated as invalid. In locales other than > ^^^^^^^^^^^^^^^^^^^^^ > : the POSIX locale, this construct has unspecified > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > : behavior. > ^^^^^^^^ >=20 > This is identical to a similar issue with awk(1), and the latest > snapshot of the One True AWK reverts to NOT using strcoll(3) to > handle character ranges in RE, because different locales and even > the same locales on different operating systems (FreeBSD, Linux, > and Solaris were compared) have different ideas about the collating > order. On Linux, the German locale's collating sequence will be > ``A a ... B b'', while on FreeBSD, it's ``A B ... a b''. This is bug in AWK, since strcoll() required in regexp, but we don't discuss AWK. Even in case it is unspecified behaviour, it means that 1) We can't use c-c for non-POSIX locales! 2) All occurances of c-c must be either replaced or used in C locale only! In other words, you win nothing, insisting on historycal behaviour, because its usage is ILLEGAL in anycase (i,e, outside of LANG=3DC) > So I'd rather prefer if we revert to the old behavior in tr(1). No way. The ranges should be similar with what we have for regexp. --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iQCVAwUBPy5xLuJgpPLZnQjrAQGmDQQAqloe1HxlrDVGUIseibcRAjXn7jINbKKv I2GtoECdIYyMb3tyZWFG8+bMnc5MTKV20/b4mgTNgmLdcTjN6SxSVtv5PwVF9aFu X5JQeA2hOF6ASU9FLyV8Q2aWc1R5Zibg3aK3CBPtVLbu15InBiYeM0iUrBv1jXpe 8sHuBRbd9fA= =0ey0 -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030804144358.GA81091>