Re: removing ereg functions

In my mind the problem that Brian raised is that ereg is slow. The solution is not to ban eregi but to fix it by performance tuning the C code. Just my 2c worth. John Lim Rasmus Lerdorf <rasmus@php.net> wrote in message news:Pine.LNX.4.33.0105160036060.990-100000@rasmus.php.net... > > That is why I am asking. Is there a core reason that the ereg functions > > have to be there? I could extend this to other functions as well of course. > > But this set in particular I have wondered about. > > 1) There was no PCRE library when I first added regex support to PHP. > Henry Spencer's regex library, although not my initial choice, was > chosen because that is what came bundled with Apache. > > 2) The ereg_* functions implement the Posix 1003.2 extended regular > expression standard. The same regular expressions found in the > Unix command line utils like grep, egrep and fgrep. The preg_* > functions support the perverted Perl-style regular expressions. > > 3) Removing the ereg_* functions would cause a backward compatibility > nightmare. Thousands, if not hundreds of thousands of scripts out > there would have to be converted. > > 4) If you are using Apache you already have the library linked in anyway. > Removing PHP support wouldn't save you any "bloat". Not that this > "bloat" is at all significant on any modern OS with shared pages. > > -Rasmus > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >