Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76614
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAESVnVr3QJ56Ynu1cN+745fZEkq+Qas=5ecvQcF0jBX7QhdaMg@mail.gmail.com>
References: <53F1094B.4040100@mabe.berlin>
	<CAESVnVr3QJ56Ynu1cN+745fZEkq+Qas=5ecvQcF0jBX7QhdaMg@mail.gmail.com>
Date: Sun, 17 Aug 2014 16:45:07 -0400
Message-ID: <CAJ5u6yi4v93nQV25Z-Ei7AtD3_4yQSyd2fnQSk-7G8AqHnz7UA@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>, Marc Bennewitz <php@mabe.berlin>
Content-Type: multipart/alternative; boundary=90e6ba1f019864955a0500d9541c
Subject: Re: [PHP-DEV] [RFC] Binary String Comparison
From: adrianguenter@gmail.com (Adrian Guenter)

--90e6ba1f019864955a0500d9541c
Content-Type: text/plain; charset=UTF-8

Type juggling is a (major) feature of PHP which would effectively be
neutered by this change. As Sara mentioned we already have tools to achieve
binary and string comparison.
On Aug 17, 2014 4:19 PM, "Sara Golemon" <pollita@php.net> 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..?
>
> -Sara
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--90e6ba1f019864955a0500d9541c--