Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30971
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.114 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 16 Jul 2007 06:46:22 -0700
Message-ID: <698DE66518E7CA45812BD18E807866CE648191@us-ex1.zend.net>
Thread-Topic: [PHP-DEV] POSIX regex
Thread-Index: AcfHp6I3lmeW2lV+TDGVosiqbf5FagAB3FnQAAAnmpA=
To: <jani.taskinen@iki.fi>,
	<internals@lists.php.net>
Subject: RE: [PHP-DEV] POSIX regex
From: andi@zend.com ("Andi Gutmans")

Why move it to PECL? I agree that PCRE is the preferred way but not
having ereg() will break a huge amount of applications for very little
gain.

We might possibly want to consider disabling by default but not having
it in the default package doesn't make real sense.

Trying to do browscap.c and pgsql.c with PCRE sounds right (if it's
possible which it probably is).
Andi=20

> -----Original Message-----
> From: Jani Taskinen [mailto:jani.taskinen@sci.fi]
> Sent: Monday, July 16, 2007 5:48 AM
> To: internals@lists.php.net
> Subject: [PHP-DEV] POSIX regex
>=20
> I have moved the POSIX regex dependant functions to ext/ereg/=20
> extension.
>=20
> Now only places using the POSIX regex functions (ext/ereg/
> excluded) are ext/standard/browscap.c and ext/pgsql/pgsql.c.
>=20
> So what to do with these 2 places using the POSIX stuff?=20
> Convert them to use PCRE functions or enable PCRE to be build with the

> POSIX compat functions?
>=20
> ext/ereg/ is going to go to PECL anyway..
>=20
> --Jani
>=20
> --
> PHP Internals - PHP Runtime Development Mailing List To unsubscribe,=20
> visit: http://www.php.net/unsub.php
>=20
>=20