Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76980
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.51 as permitted sender)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0C1B8793-A635-492C-96EF-939CBFF8E8DB"
Message-ID: <137F7EB5-9A04-4780-A5F7-31089DEC959C@gmail.com>
Date: Sun, 31 Aug 2014 13:08:00 +0800
To: PHP Internals <internals@lists.php.net>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Kill ereg with fire
From: tjerk.meesters@gmail.com (Tjerk Meesters)

--Apple-Mail=_0C1B8793-A635-492C-96EF-939CBFF8E8DB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi internals (again),

Recently I=92ve 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=92ve replaced two instances of ereg with their pcre equivalents, =
OPcache and PGSQL.

Btw, simply using =91pcreposix.h=92 didn=92t work out for OPcache, I =
would get this error:

Error Blacklist compilation: invalid argument to regex routine

Perhaps I=92ve missed something obvious, but porting it wasn=92t hard =
either.

Thoughts?=

--Apple-Mail=_0C1B8793-A635-492C-96EF-939CBFF8E8DB--