On Sun, Feb 5, 2012 at 19:32, Adam Harvey <ahar...@php.net> wrote: > On 6 February 2012 04:37, Tom Boutell <t...@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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
