Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29870
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.235 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=c3VXEVlHEu3LndNLktkMYexm6EKxEEH2lhpDleelSCWFhB786zm9u7cWgAdScMatkj+gbE4AlCxlTGPZ6k2MF5c2HPBrlktHIXcvnnJ4azRCP2JaZS1HzWYoaZAk1fpecN9CEKWc+qGberEBvMK3R6+L/pE9uN2XlBcd8L1/rWc=
Message-ID: <fe05d1540705290824u4f658e50j8a410dfe90a101@mail.gmail.com>
Date: Tue, 29 May 2007 17:24:49 +0200
To: "David Coallier" <davidc@php.net>
Cc: "Antony Dovgal" <antony@zend.com>, php-dev <internals@lists.php.net>
In-Reply-To: <b5f7bf6c0705290806s1fa8311dg30077491ec3956df@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <465BF195.2080300@zend.com>
	 <b5f7bf6c0705290806s1fa8311dg30077491ec3956df@mail.gmail.com>
Subject: Re: [PHP-DEV] bitwise operations and Unicode strings
From: pierre.php@gmail.com (Pierre)

Hi,

On 5/29/07, David Coallier <davidc@php.net> wrote:
> On 5/29/07, Antony Dovgal <antony@zend.com> wrote:
> > Hello.
> >
> > Do you think the engine should support bitwise operators and Unicode strings?
> > If yes, how do you think it should work?
> >
> > Example:
> > <?php
> > $a = "1";
> > $a|="2";
> > var_dump($a);
> > ?>
> >
> > This code outputs "3" in native mode and "Fatal error: Unsupported operand types" in Unicode mode.
> > I believe this is an inconsistency and it should be possible to use Unicode strings there.
>
> Definitely
>
> >
> > There are several possible ways to implement it:
> > 1) the same as with native strings - apply the operator to each element of the string separately;
> > 2) convert the string to binary (using say iso-8859-1) and then see 1);
>
> I would probably be for the solution #2 and of course using the
> unicode.runtime_encoding ini setting to convert it to binary.
>
>
> >
> > We can also leave it as is (since it doesn't seem very useful) or even drop the native strings support (it doesn't seem very useful to me either).
>
> I think this is a bad choice.. might not be useful to you, but might
> be to some other people

I fail to see or imagine any useful usages for such hacks. Laziness
justifies it with binary strings (as in 5.x), but as long as an
unicode string is given, one should really first cast to integer
before using it with a bitwise operator (or any other non string
operation).

I'm in favour of keeping the current behaviors and drop the native
support as well for consistency (and documentation/wtf headaches).

--Pierre