Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30368 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98282 invoked by uid 1010); 29 Jun 2007 17:42:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 98267 invoked from network); 29 Jun 2007 17:42:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jun 2007 17:42:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=andrei@gravitonic.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=andrei@gravitonic.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain gravitonic.com from 204.11.219.139 cause and error) X-PHP-List-Original-Sender: andrei@gravitonic.com X-Host-Fingerprint: 204.11.219.139 mail.lerdorf.com Received: from [204.11.219.139] ([204.11.219.139:53013] helo=mail.lerdorf.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5A/D9-21469-D8445864 for ; Fri, 29 Jun 2007 13:42:38 -0400 Received: from [192.168.30.114] ([207.7.138.44]) (authenticated bits=0) by mail.lerdorf.com (8.14.1/8.14.1/Debian-7) with ESMTP id l5THgX9l029717; Fri, 29 Jun 2007 10:42:34 -0700 In-Reply-To: <41782.78.61.224.253.1183107677.squirrel@avilys.eik.lt> References: <1181829227.3478.3.camel@localhost.localdomain> <7d5a202f0706141844l3c75b556hdbecbcd5a43747c9@mail.gmail.com> <4671F184.2020401@lerdorf.com> <6sof73dj69ldpspfc5ukrc58qr9ckbin2b@4ax.com> <4677E7B1.2080305@lerdorf.com> <4677F5FB.1070206@lerdorf.com> <4678252F.2050803@sci.fi> <46783212.4020900@lerdorf.com> <34654.216.230.84.67.1183064088.squirrel@www.l-i-e.com> <54557.78.61.224.253.1183098089.squirrel@avilys.eik.lt> <4684BB91.4070507@zend.com> <41782.78.61.224.253.1183107677.squirrel@avilys.eik.lt> Mime-Version: 1.0 (Apple Message framework v752.2) X-Priority: 3 (Normal) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: <7A19D00A-9A46-4854-8C5E-26C8F8FAC4B5@gravitonic.com> Cc: internals@lists.php.net Content-Transfer-Encoding: 7bit Date: Fri, 29 Jun 2007 10:42:31 -0700 To: Tomas Kuliavas X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: ClamAV 0.90.3/3556/Fri Jun 29 09:23:10 2007 on colo.lerdorf.com X-Virus-Status: Clean Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6? From: andrei@gravitonic.com (Andrei Zmievski) It sounds like your libraries are definitely oriented towards working with binary strings, rather than Unicode strings. So, I am not sure why you have unicode.semantics turned on then. If you turn it off, you will get backwards compatibility with PHP 5. And if you do that, you can still create and work on Unicode strings, programmatically. -Andrei On Jun 29, 2007, at 2:01 AM, Tomas Kuliavas wrote: > > If I write "\xA0", I expect one byte with A0 hex value and not 0xC2 > \xA0 > (\u00A0). If I use \x80-\xFF range, I expect functions to match > bytes and > not only \u0080 - \u00FF > > Binary strings can do that, but they are not backwards compatible. In > order to do same thing in PHP4/5 and PHP6, I'll have to move code into > separate libraries.