Re: [RFC] Deprecate and remove /e modifier from preg_replace

From: Date: Mon, 06 Feb 2012 01:58:59 +0000
Subject: Re: [RFC] Deprecate and remove /e modifier from preg_replace
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-57757@lists.php.net to get a copy of this message
On Sun, Feb 5, 2012 at 19:32, Adam Harvey <aharvey@php.net> wrote: > 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 — I'd rather be actively trying to kill some of > that than ushering more in. Strong +1 from me as well. Deprecate, remove. Do NOT get Suhoshin involved in this. It's not. -- Gwynne

« previous php.internals (#57757) next »