Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48586 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98789 invoked from network); 31 May 2010 17:31:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 May 2010 17:31:31 -0000 Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain adamharvey.name from 209.85.212.42 cause and error) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:56524] helo=mail-vw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 35/71-26688-372F30C4 for ; Mon, 31 May 2010 13:31:31 -0400 Received: by vws12 with SMTP id 12so327205vws.29 for ; Mon, 31 May 2010 10:31:28 -0700 (PDT) Received: by 10.224.72.15 with SMTP id k15mr1827845qaj.356.1275327088214; Mon, 31 May 2010 10:31:28 -0700 (PDT) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.229.220.9 with HTTP; Mon, 31 May 2010 10:31:08 -0700 (PDT) In-Reply-To: <1275326628.24497.1.camel@guybrush> References: <4BD87B5C.4020902@no-surprises.co.uk> <1275326628.24497.1.camel@guybrush> Date: Tue, 1 Jun 2010 01:31:08 +0800 X-Google-Sender-Auth: ZRMYychWjUwiFTBZ2rZ4kQ4nNBw Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= Cc: Felipe Pena , Michael Maclean , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] ereg deprecation? From: aharvey@php.net (Adam Harvey) 2010/6/1 Johannes Schl=C3=BCter : > On Mon, 2010-05-31 at 14:09 -0300, Felipe Pena wrote: >> I think make no sense to keep it deprecated. >> >> Here's a patch for undeprecate ext/ereg in 5_3 and trunk: >> http://felipe.ath.cx/diff/undeprecate-ereg.diff >> >> Any objection? If no, I'll commit it in soon. > > I still won't recommend using ereg - the missing binary-safety causes > quite some broken checks ... is there anything that can be done which > can't be done using pcre? If not: Less code to maintain -> less > trouble :-) I believe PCRE's generally quicker into the bargain anyway. We've already told people we're killing ereg, and there are good reasons to do so regardless of Unicode (lack of binary safety being the main one, with the needless duplication with PCRE being another). Let's keep it deprecated and kill it when it makes sense to do so (next major, or if and when Unicode comes back at some future date). Adam