Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76989
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <E0D355FD-C645-49E6-A1AA-BC28B2A556CE@gmail.com>
References: <137F7EB5-9A04-4780-A5F7-31089DEC959C@gmail.com>
	<CAH-PCH64H0NL_vDbDSMsDBZ9pDXDHJEzdpnU7NT79ed3u+zdSQ@mail.gmail.com>
	<E0D355FD-C645-49E6-A1AA-BC28B2A556CE@gmail.com>
Date: Sun, 31 Aug 2014 16:32:13 +0200
Message-ID: <CAEZPtU68QsaNQEOQqFWA5DD9WQJq66K9yyLthSKuc7Le=ZVxZA@mail.gmail.com>
To: Tjerk Meesters <tjerk.meesters@gmail.com>
Cc: PHP internals <internals@lists.php.net>, Ferenc Kovacs <tyra3l@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ab2ec989a490501edc073
Subject: Re: [PHP-DEV] Kill ereg with fire
From: pierre.php@gmail.com (Pierre Joye)

--001a113ab2ec989a490501edc073
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Heck... No :)

Or we mark it as dead right away, single release for the sake of it and let
it die.
On Aug 31, 2014 2:08 PM, "Tjerk Meesters" <tjerk.meesters@gmail.com> wrote:

> Hi Ferenc,
>
> On 31 Aug, 2014, at 7:00 pm, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>
> >
> >
> >
> > On Sun, Aug 31, 2014 at 7:08 AM, Tjerk Meesters <
> tjerk.meesters@gmail.com> wrote:
> > Hi internals (again),
> >
> > Recently I=E2=80=99ve done a small assessment on how feasible it is to =
remove
> ext/ereg from the project for the next major version. This is the result
> (so far):
> >
> > https://github.com/datibbaw/php-src/compare/kill-ereg
> >
> > I=E2=80=99ve replaced two instances of ereg with their pcre equivalents=
, OPcache
> and PGSQL.
> >
> > Btw, simply using =E2=80=98pcreposix.h=E2=80=99 didn=E2=80=99t work out=
 for OPcache, I would get
> this error:
> >
> > Error Blacklist compilation: invalid argument to regex routine
> >
> > Perhaps I=E2=80=99ve missed something obvious, but porting it wasn=E2=
=80=99t hard either.
> >
> > Thoughts?
> >
> > Afair we have a patch floating around, but never made it into the repo,
> but everybody seemed to agree to remove the core dependency of ereg and
> make it optional to enable.
>
> You mean make it optional to install via PECL, right? I agree ;-)
>
> Package maintainers can always choose to ship their php packages with ere=
g
> as a means to keep supporting it, regardless of how it=E2=80=99s provided=
 (bundled
> or PECL).
>
> >
> >
> > --
> > Ferenc Kov=C3=A1cs
> > @Tyr43l - http://tyrael.hu
>
>

--001a113ab2ec989a490501edc073--