Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73129 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91365 invoked from network); 13 Mar 2014 20:36:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Mar 2014 20:36:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 198.187.29.241 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 198.187.29.241 imap3-1.ox.registrar-servers.com Received: from [198.187.29.241] ([198.187.29.241:37326] helo=imap3-1.ox.registrar-servers.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A3/28-47923-6E612235 for ; Thu, 13 Mar 2014 15:36:55 -0500 Received: from localhost (localhost [127.0.0.1]) by oxmail.registrar-servers.com (Postfix) with ESMTP id F2A162A0084; Thu, 13 Mar 2014 16:36:51 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap3.ox.registrar-servers.com Received: from oxmail.registrar-servers.com ([127.0.0.1]) by localhost (imap3.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NPBncGbVMIib; Thu, 13 Mar 2014 16:36:51 -0400 (EDT) Received: from [192.168.0.8] (unknown [90.203.28.187]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oxmail.registrar-servers.com (Postfix) with ESMTPSA id F0D772A0083; Thu, 13 Mar 2014 16:36:47 -0400 (EDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_1FFD68D7-A200-4848-AA0A-F527C0488CF1" Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) In-Reply-To: Date: Thu, 13 Mar 2014 20:36:41 +0000 Cc: Stas Malyshev , Crypto Compress , PHP Developers Mailing List Message-ID: <4319DC6B-1983-4121-BF47-4740DB19A8DD@ajf.me> References: <531EE602.3090207@lsces.co.uk> <531EEE2A.2000602@googlemail.com> <531F0146.5010701@lsces.co.uk> <53202DC5.4010306@googlemail.com> <532033E1.60602@lsces.co.uk> <53203687.7090405@googlemail.com> <532037F4.6020204@googlemail.com> <532049BB.2080605@lsces.co.uk> <53204C6B.3000506@googlemail.com> <5320511A.7040606@lsces.co.uk> <5320F554.5000109@lerdorf.com> <53210857.5040908@googlemail.com> <53220E2D.2080605@sugarcrm.com> To: Yasuo Ohgaki X-Mailer: Apple Mail (2.1874) Subject: Re: [PHP-DEV] Unicode strings? From: ajf@ajf.me (Andrea Faulds) --Apple-Mail=_1FFD68D7-A200-4848-AA0A-F527C0488CF1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 13 Mar 2014, at 20:32, Yasuo Ohgaki wrote: >=20 > I agree with your argument in general, but restricting pattern will = break > existing scripts which are working now. If >=20 > $caf=E9 !=3D=3D $caf=E9 > 0x63 0x61 0x66 0xC3 0xA9 > 0x63 0x61 0x66 0x65 0xCC 0x81 >=20 > is issue. It's current issue. Do we really have to care about this and > introduce BC? It seems documentation would be enough. Writing programs in other languages is generally bad practise anyway. I = don=92t think PHP should encourage it if it will cause problems. This would introduce BC breaks, yes, but I suppose you could probably = write a program to change identifier names. -- Andrea Faulds http://ajf.me/ --Apple-Mail=_1FFD68D7-A200-4848-AA0A-F527C0488CF1--