Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71255 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54473 invoked from network); 18 Jan 2014 21:17:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jan 2014 21:17:23 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:46759] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 93/61-46720-16FEAD25 for ; Sat, 18 Jan 2014 16:17:22 -0500 Received: (qmail 23201 invoked by uid 89); 18 Jan 2014 21:17:17 -0000 Received: by simscan 1.3.1 ppid: 23190, pid: 23198, t: 0.0535s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 18 Jan 2014 21:17:17 -0000 Message-ID: <52DAEFEF.9090705@lsces.co.uk> Date: Sat, 18 Jan 2014 21:19:43 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 MIME-Version: 1.0 To: "internals@lists.php.net" References: <52DA84A2.2050305@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Multibyte char handling From: lester@lsces.co.uk (Lester Caine) Yasuo Ohgaki wrote: > I'm not proposing transition like Python 2.x to 3.x. The RFC is proposing > required feature for proper/safe coding. Anyway, it seems Python's approach is > not working well. We could learn from it. I am more than convinced that is a perfect example of how not to do it, but there surly is no reason to make such a mess of 'PHP6' over PHP5? I have to be able to program in Python for some of the tools, and they have no plans to move to 3.x any time soon :) -- 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