Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54617
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.125 cause and error)
Message-ID: <4E48D6E7.2000203@lsces.co.uk>
Date: Mon, 15 Aug 2011 09:20:55 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-2.2 SeaMonkey/2.0.14
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
References: <CABBJUpfez0_CKkiFSVVmYfxbF7H30Av2y9D1Nww6PE5v6dKPUw@mail.gmail.com>	<CAM4sM9Hxn=2FJ4d51ozbKuGM4e3BMMUQ38WsEs27WAu919XSjg@mail.gmail.com>	<CABBJUpdONFHHYpdr4RvxGRyJ13M9yONVzb-aSjx33QKziALkLA@mail.gmail.com>	<CABBJUpeoDnuT7eXC6UzUFQni0V0zH_mivHiX=3j=UjCKJK-z7Q@mail.gmail.com>	<CABBJUpdXUOjyWpXeRovNaFgDMQHfM5MkXXto+Rybej2u+W4xFw@mail.gmail.com>	<alpine.DEB.2.02.1108141219470.4043@whisky>	<CAH-PCH6_sTBGqCrCp-pgdi3DJfFX-3ZsvSr8ibbrOtKQP0qpTA@mail.gmail.com>	<alpine.DEB.2.02.1108141359340.4043@whisky>	<4E48121A.3090007@sugarcrm.com>	<4E48134E.4030708@sugarcrm.com>	<4E481695.6040900@php.net>	<4E483804.7070009@sugarcrm.com>	<4E484037.2080107@php.net>	<4E4843B0.70605@php.net>	<CABBJUpfmV23H2MgkCi60MeLN1dp9Qe+aJJj1y9F0GWfSXL_ygA@mail.gmail.com>	<CAHMUw2ENKWjgQH_-eA4uP94yjw1pvQ50OoEUx+wZ5AmwhMfEoA@mail.gmail.com> <CABBJUpcO25NHLpttro+OaEvG0Unf+us1q+wn2fpKy6XzpfUA4A@mail.gmail.com>
In-Reply-To: <CABBJUpcO25NHLpttro+OaEvG0Unf+us1q+wn2fpKy6XzpfUA4A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE]strn(case)cmp supporting a negative length as
 its third paramter
From: lester@lsces.co.uk (Lester Caine)

Laruence wrote:
>     yes,  substr_compare can do it, and it also supports negative
> length argument too.

I am with Rasmus ... while the BC problem he is pointing out is probably very 
rare, those are the worse ones to fix when they pop up intermittently, and 
usually when 10 year old code has been working fine and suddenly starts doing it?

All of the original base str... functions currently follow the libc manual ( I 
think ) and that is how they work. My first thought when the thread started was 
that this needed a different name - which is exactly why substr_compare exists? 
Although nothing is appearing in my archive, I'm sure that this discussion has 
already happened long ago when this was added to PHP5? Perhaps it should be 
linked in the SeeAlso from strncmp and the rest?

 >     but I am proposal to improve strn(case)cmp, so they are not  conflict .:)

One persons improvement can become someone elses BC nightmare?

I seem to recall a discussion about tidying up many of the string functions, 
probably part of unicode compatibility, and in that vane, would it be possible 
to create a 'namespace' version of string functions which could be a little more 
consistent, and also offer the chance to switch to full unicode comparison if 
required? sb:: -> mb:: transparently working the same way? needle and haystack 
order comes to mind as well?

Is there any reason there is not an mb_substr_compare ?
Yes character based rather than byte. Seems to me that this is the way to go 
rather than changing the other functions? Actually substr_compare will tidy up a 
bit of a mess in my own code where I need to switch case on and off I'd just not 
remembered it existed ....

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php