Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76611
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mabe.berlin from 80.237.132.171 cause and error)
Message-ID: <53F1094B.4040100@mabe.berlin>
Date: Sun, 17 Aug 2014 21:58:03 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [RFC] Binary String Comparison
From: php@mabe.berlin (Marc Bennewitz)

Hi internals!

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

On comparing two numeric strings both operands will be equal if the 
string representation will be the same. On comparing two numeric strings 
the first operand will be greater if the first not matching byte will be 
higher. On comparing two numeric strings the first operand will be lower 
if the first not matching byte will be lower.

As a side effect it makes string comparison much faster and force 
developer to really write what they mean (No need to guess) and to force 
developers to cast/filter input once which also affects performance.

On C-Level the function zendi_smart_strcmp will be unused and marked as 
deprecated.

Thanks,
Marc