Re: [PHP-DEV] Kill ereg with fire

[email protected] (Chris Wright)
Newsgroups php.internals
Message-ID <CAGAGxbbd+jG9p-byEb-Vup2HSLh1HyY4x2dyhBP3RNh9MrpatA@mail.gmail.com>
I have on occasion come across code that uses split(), more often than not
as if it were explode() with a literal delimiter.

If ereg is to be removed (for which I am +1) does anyone have any
objections to making split() into an alias of explode()? This would also be
consistent with the join() -> implode() alias.

Ps. Sorry for top reply, my phone doesn't seem to want to play nice with an
in line response.
On 31 Aug 2014 17:29, "Levi Morrison" <[email protected]> wrote:

> On Sun, Aug 31, 2014 at 8:32 AM, Pierre Joye <[email protected]> wrote:
> > Heck... No :)
> >
> > Or we mark it as dead right away, single release for the sake of it and
> let
> > it die.
>
> I think a single, unmaintained release of ext/ereg in PECL would be
> acceptable, but I don't really see the point of that either. If you
> still rely on ereg you probably can't upgrade from an earlier version
> of PHP so you'll end up using an old release which already has ereg.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.