what I mean is that, as far as I remember, the deprecation is only an information via the documentation. We did not want to break BC and all that as it is now emulated through pcre.
On Tue, Jan 10, 2012 at 4:46 PM, Philip Olson <phi...@roshambo.org> wrote: > Hello Pierre, > > I mean that the ereg extension is deprecated, yet we cannot disable > it while compiling PHP. In other words, ereg() and friends always > exist in PHP, and emit E_DEPRECATED errors upon use. We should have > the option of creating fatal undefined function errors… basically. > > Currently this exists for ereg: > > --with-regex[=TYPE] > > So I guess we want: > > --without-regex > > Even though --disable-ereg would feel more natural. > > Regards, > Philip > > On Jan 10, 2012, at 12:27 AM, Pierre Joye wrote: > >> is it not emulated using pcre now? as in, the ereg library is not used >> anymore >> >> On Tue, Jan 10, 2012 at 8:49 AM, Philip Olson <phi...@roshambo.org> wrote: >>> Hi geeks! >>> >>> We're unable to disable the ereg extension today, yet it's been deprecated >>> since PHP 5.3.0. Is this by design? >>> >>> Regards, >>> Philip >>> >>> >>> -- >>> PHP Internals - PHP Runtime Development Mailing List >>> To unsubscribe, visit: http://www.php.net/unsub.php >>> >> >> >> >> -- >> Pierre >> >> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
