Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48588
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=hIZQuQxfimmARm6VKROGxZW18shnTUQSNNzyu+zbvZHvEXBwo7nOscHaSEPp6JCt7J
         IRVVGW4en82C2+7xQqj3/Xp1CoPn3beJ9ok2b36Odr5N5bFDqyMzRj70aDHomOaURfMA
         5VX2qRctcSgzUO4MfObjxZcCse/WgY/DFhtO8=
MIME-Version: 1.0
In-Reply-To: <1275326628.24497.1.camel@guybrush>
References: <4BD87B5C.4020902@no-surprises.co.uk>
	<AANLkTilL7TLXHzUWcQIBUC6PzOD5HnudAmV4HQu_RNG8@mail.gmail.com>
	<1275326628.24497.1.camel@guybrush>
Date: Mon, 31 May 2010 18:45:17 -0300
Message-ID: <AANLkTinFws9UWRBHh5Ucyypqe7HIBrwF6FCggsLjGfv_@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Michael Maclean <michael@no-surprises.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=0016e6546f1ed567ef0487eac5be
Subject: Re: [PHP-DEV] ereg deprecation?
From: felipensp@gmail.com (Felipe Pena)

--0016e6546f1ed567ef0487eac5be
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2010/5/31 Johannes Schl=C3=BCter <johannes@schlueters.de>

> On Mon, 2010-05-31 at 14:09 -0300, Felipe Pena wrote:
> > Hi,
> >
> > 2010/4/28 Michael Maclean <michael@no-surprises.co.uk>
> >
> > > Hi,
> > > I think I asked this before on IRC, but I've forgotten the answer. I
> was
> > > just remembering that the ereg extension was due to be deprecated in
> PHP6 -
> > > does this still apply to trunk?
> > >
> > >
> > I think make no sense to keep it deprecated.
> >
> > Here's a patch for undeprecate ext/ereg in 5_3 and trunk:
> > http://felipe.ath.cx/diff/undeprecate-ereg.diff
> >
> > Any objection? If no, I'll commit it in soon.
>
> I still won't recommend using ereg - the missing binary-safety causes
> quite some broken checks ... is there anything that can be done which
> can't be done using pcre? If not: Less code to maintain -> less
> trouble :-)
>
>
I also won't recommend using ereg, I just thought the unique reason to
deprecate it was the unicode stuff, hence wouldn't make sense to keep it
deprecated... But as there are others motivations, I prefer leave as is too=
.

--=20
Regards,
Felipe Pena

--0016e6546f1ed567ef0487eac5be--