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_comparisonIf 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 ==, <, >?".
We have a standard way to compare two operands but currently we do some magic things to solve something that don't need to be solved.
If you would like to compare two pears we currently convert the pears into apples and compare two apples and say please use a special function to compare two pears. Why?
There is no numeric context to compare two strings numerically.
-Sara
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
