Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76651
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53F1F534.50109@mabe.berlin>
References: <53F1094B.4040100@mabe.berlin>
	<CAESVnVr3QJ56Ynu1cN+745fZEkq+Qas=5ecvQcF0jBX7QhdaMg@mail.gmail.com>
	<53F1F534.50109@mabe.berlin>
Date: Mon, 18 Aug 2014 14:53:51 +0200
Message-ID: <CAEZPtU4yd8RHiFi0cDzk0Vm2WTS-ayUgKdczTEjG986Bp8zgnw@mail.gmail.com>
To: Marc Bennewitz <php@mabe.berlin>
Cc: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Binary String Comparison
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Mon, Aug 18, 2014 at 2:44 PM, Marc Bennewitz <php@mabe.berlin> wrote:
>
>
> On 17.08.2014 22:18, Sara Golemon wrote:
>>
>> On Sun, Aug 17, 2014 at 12:58 PM, Marc Bennewitz <php@mabe.berlin> wrote:
>>>
>>> I've created a draft RFC and patch to change the behavior of non-strict
>>> string to string comparison to be binary safe (as the strict comparison
>>> operator does):
>>>
>>>       https://wiki.php.net/rfc/binary_string_comparison
>>>
>> If I understand your goal correctly, you seem to want to change a very
>> fundamental (and ancient) behavior of the language even though
>> mechanisms already exist to do what you describe as the "changed
>> behavior".
>>
>> What exactly is wrong with ===, strcmp(), etc..?
>
>
> The question isn't "What's wrong with ===, strcmp()?" but "What's wrong with
> ==, <, >?".

And the answer is: not strict and why === exists.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org