Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29872 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78828 invoked by uid 1010); 29 May 2007 15:38:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 78813 invoked from network); 29 May 2007 15:38:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 May 2007 15:38:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=antony@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=antony@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender) X-PHP-List-Original-Sender: antony@zend.com X-Host-Fingerprint: 212.25.124.162 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from [212.25.124.162] ([212.25.124.162:22278] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4B/00-10662-7D84C564 for ; Tue, 29 May 2007 11:38:02 -0400 Received: (qmail 18775 invoked from network); 29 May 2007 15:37:56 -0000 Received: from internal.zend.office (HELO ?127.0.0.1?) (10.1.1.1) by internal.zend.office with SMTP; 29 May 2007 15:37:56 -0000 Message-ID: <465C48D3.9080407@zend.com> Date: Tue, 29 May 2007 19:37:55 +0400 User-Agent: Thunderbird 2.0.0.0 (X11/20070326) MIME-Version: 1.0 To: RQuadling@GoogleMail.com CC: Pierre , David Coallier , php-dev References: <465BF195.2080300@zend.com> <10845a340705290830y337a050amfc3cac12a66eb1b7@mail.gmail.com> In-Reply-To: <10845a340705290830y337a050amfc3cac12a66eb1b7@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] bitwise operations and Unicode strings From: antony@zend.com (Antony Dovgal) On 29.05.2007 19:30, Richard Quadling wrote: > As PHP is loosely typed, "1"==1 is fine. Right, but that's not true for bitwise operators. Try this: and this OR is applied to _characters_ of the string. Hence I can see no reason to support it at all. > Is it that with Unicode, this looseness is gone? Nope. -- Wbr, Antony Dovgal