Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78193 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19714 invoked from network); 21 Oct 2014 10:19:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2014 10:19:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:50494] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 21/A3-02077-B4336445 for ; Tue, 21 Oct 2014 06:19:56 -0400 Received: (qmail 27442 invoked by uid 89); 21 Oct 2014 10:19:53 -0000 Received: by simscan 1.3.1 ppid: 27431, pid: 27437, t: 0.3435s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.178.187.131) by mail4.serversure.net with ESMTPA; 21 Oct 2014 10:19:52 -0000 Message-ID: <54463347.6020002@lsces.co.uk> Date: Tue, 21 Oct 2014 11:19:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: internals@lists.php.net References: <1413875212.2624.3.camel@localhost.localdomain> <1413883549.2624.22.camel@localhost.localdomain> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] UString From: lester@lsces.co.uk (Lester Caine) On 21/10/14 10:52, Dmitry Stogov wrote: >> That seems a lot like bashing our head against a wall. We tried to >> > introduce support everywhere and it fails. Do we really want to step on >> > the performance gains introduced by recent changes by making all strings >> > unicode ? >> > > Yeah :) > I'm not sure, if it should be done, and I don't like to work on it in the > nearest future, but zend_string approach should be easier to implement than > separate IS_UNICODE + IS_STRING + IS_BINARY types in PHP6. Isn't this the first discussion? If we are going down the root of keeping PHP7 as ascii only in the core, then ustring probably makes sense, but it does not address many of the areas where unicode is really needed. Handling unicode content outside the core is working reasonably at the moment, it is the problems such as using unicode keys for arrays which is the main area where unicoe is needed in PHP7 and so a more embedded handling is needed which may cut across yet another content wrapper? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk