]> granicus.if.org Git - php/commit
Doing a strnatcasecmp(chr(128),chr(255)) is completely non-sensical.
authorRasmus Lerdorf <rasmus@php.net>
Sat, 8 Aug 2009 14:48:47 +0000 (14:48 +0000)
committerRasmus Lerdorf <rasmus@php.net>
Sat, 8 Aug 2009 14:48:47 +0000 (14:48 +0000)
commit53349c7769c2100d0c23d3fe444de33039d97166
treee33ef12adece1db5f40446d326a6d5c82070ff76
parent124a0a5a692120e12cf90743998761b0be4ca894
Doing a strnatcasecmp(chr(128),chr(255)) is completely non-sensical.
Logically one might think that chr(128) would collate before chr(255) except
this is a case-insensitive comparison and internally we toupper() both args.
toupper(chr(128)) is 128.  There is no upper-case equivalent of this char.
toupper(chr(255)) is 120 so chr(255) collates before chr(128) in this
case-insensitive comparison.  And these are rather bogus characters to feed
to a natsort test anyway.
ext/standard/tests/strings/strnatcasecmp_variation1.phpt