On Tue, 2012-01-10 at 18:28 +0100, Pierre Joye wrote: > 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.
There is no emulation, the behavior of the ereg library and pcre is different that emulation is not possible in a useful way. It is also not only in documentation but by throwing E_DEPRECATED. > > Currently this exists for ereg: > > > > --with-regex[=TYPE] > > > > So I guess we want: > > > > --without-regex > > > > Even though --disable-ereg would feel more natural. --disable is the counterpart to --enable as generated by autoconf. --without the counterpart to --with. We use --with for things using some library. ereg uses by default a bundled library but could also be configured to use a system configured library. Therefor "--with" is correct, therefore --without is the "correct" consequence. > >>> We're unable to disable the ereg extension today, yet it's been > >>> deprecated since PHP 5.3.0. Is this by design? It's at least partly by design. We had some code using ereg library stuff internally, so core PHP depended on it. The plan was to rewrite these code parts to use pcre. I'm not sure that has been done, yet. Till then we can't make ereg optional. We should look into this for 5.5, using ereg is a bit dangerous (0-byte safety etc.) so dropping it is a good thing, even aside from reducing the amount of code to maintain. johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
