Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30201
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain gravitonic.com from 204.11.219.139 cause and error)
In-Reply-To: <465BF195.2080300@zend.com>
References: <465BF195.2080300@zend.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <BF854DAD-57CA-4D2C-B3CE-9CFE2ABC0A6D@gravitonic.com>
Cc: php-dev <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Date: Fri, 15 Jun 2007 18:58:42 -0700
To: Antony Dovgal <antony@zend.com>
Subject: Re: [PHP-DEV] bitwise operations and Unicode strings
From: andrei@gravitonic.com (Andrei Zmievski)

I don't think we should support bitwise ops on Unicode strings. I am  
not even sure why we support them for normal strings.

-Andrei


On May 29, 2007, at 2:25 AM, Antony Dovgal 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.
>
> 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);
>
> 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).
> Opinions?
>
> -- 
> Wbr, Antony Dovgal
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php