Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57755
Return-Path: <adam@adamharvey.name>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 87379 invoked from network); 6 Feb 2012 00:33:16 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 6 Feb 2012 00:33:16 -0000
Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.210.170 as permitted sender)
X-PHP-List-Original-Sender: adam@adamharvey.name
X-Host-Fingerprint: 209.85.210.170 mail-iy0-f170.google.com  
Received: from [209.85.210.170] ([209.85.210.170:48761] helo=mail-iy0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 02/03-60839-BCF1F2F4 for <internals@lists.php.net>; Sun, 05 Feb 2012 19:33:16 -0500
Received: by iakk32 with SMTP id k32so8781682iak.29
        for <internals@lists.php.net>; Sun, 05 Feb 2012 16:33:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=adamharvey.name; s=google;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:cc:content-type
         :content-transfer-encoding;
        bh=XfD4UYguWoWSPsey4CgFCUupTdsri02OKnp90skoT/I=;
        b=IJb3XjYiZ5Jrcpl33EaCSgTQBlPF2gyk8CVNU56JI8DRStlorvWGTrCg21kjBNFfUg
         /7ddydirXac10gqnW2CU09Q9l4xiuwgs6tbkFVwn+MtBtzUjr0WLZJEDM6E9CFN69g7n
         poByB4s4UD44rGmcWuv2MEZ9b16/nW69M+boI=
Received: by 10.50.203.100 with SMTP id kp4mr18615445igc.6.1328488393358; Sun,
 05 Feb 2012 16:33:13 -0800 (PST)
MIME-Version: 1.0
Sender: adam@adamharvey.name
Received: by 10.43.50.131 with HTTP; Sun, 5 Feb 2012 16:32:53 -0800 (PST)
In-Reply-To: <CAORXhGK=adtVyXL5vZZyRLLz5c8J_y6Cz4rkPwfxBFXUcRm65Q@mail.gmail.com>
References: <CAF+90c9qoyzBf+FpBxMdX0FByy5xB+7x3xi3kNxdvWX=_uz=mg@mail.gmail.com>
 <alpine.DEB.2.02.1202051644220.12865@whisky.home.derickrethans.nl>
 <A633CF2D7C7BED41B41F1E64F25507B8069D29BD20@MAILR001.mail.lan>
 <4F2EE658.2010504@sugarcrm.com> <CAORXhGK=adtVyXL5vZZyRLLz5c8J_y6Cz4rkPwfxBFXUcRm65Q@mail.gmail.com>
Date: Mon, 6 Feb 2012 08:32:53 +0800
X-Google-Sender-Auth: tESz8tA8HmxUlIKsmFX_RDJlK_Y
Message-ID: <CADajX4DNP0=X4TrEn3SsiHU4dULCssQxMW-A-PrksqfGS-As7g@mail.gmail.com>
To: Tom Boutell <tom@punkave.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Deprecate and remove /e modifier from preg_replace
From: aharvey@php.net (Adam Harvey)

On 6 February 2012 04:37, Tom Boutell <tom@punkave.com> wrote:
> Deprecate and then remove, or just leave it in. "Make it optional
> forever" just generates more nonportable PHP code. Ick.

Huge +1 to that.

Given the existence of preg_replace_callback() (as Stas noted above),
my preference is for deprecation and then removal, but I think the
overriding goal should be not introducing any more configuration
dependent behaviour =E2=80=94 I'd rather be actively trying to kill some of
that than ushering more in.

Adam