Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45748
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain arvo.suso.org from 66.244.94.5 cause and error)
Date: Mon, 12 Oct 2009 16:08:56 +0000
To: internals@lists.php.net
Message-ID: <20091012160854.GK5179@arvo.suso.org>
References: <20091012154610.GJ5179@arvo.suso.org> <bcb7aa500910120851v5b3ee96ew3c9ac8419eefd972@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <bcb7aa500910120851v5b3ee96ew3c9ac8419eefd972@mail.gmail.com>
User-Agent: Mutt/1.5.11
Subject: Re: [PHP-DEV] Why is ereg being deprecated?
From: mark@suso.org (Mark Krenz)


  Ok, let me first say that I have no problem with deprecating it in
favor of PCRE.  Being a heavy Perl developer too, I'm more used to PCRE
syntax anyways so it will be easier to only remember one syntax between
languages.

  Secondly, I've been using PHP since version 2 and as far as I can
remember ereg and the POSIX regex syntax has been in PHP for that long
if not as long as PHP has existed.

  Deprecating functionality in software is tricky enough when its a
minor function, but when its a major function in a major programming
language it is something entirely different.  Removing a function
because its fat, slow and doesn't have unicode support isn't enough of a
justification for removing a major function like ereg that is used in
probably 90% of all PHP applications. If there was some kind of
security issue that couldn't be fixed without removing it then that
would be different, but from what you said I don't think there is.

  PHP 6 already has some major changes to it that will affect many
people and slow its adoption.  Removing ereg might kill adoption of it
altogether or run the risk of PHP being forked. =20

  My suggestion is that you delay removal of the function until PHP 7 or
even 8. This will give people a lot more time to learn about change and
most major app developers will find out about it and make the change.
Also, distributions that package PHP will have at least a couple minor
versions released prior to it being removed, which I think is VERY
important.

  Please, let's discuss this.

  Mark

On Mon, Oct 12, 2009 at 03:51:48PM GMT, Guilherme Blanco [guilhermeblanco@g=
mail.com] said the following:
> It was fat, slow and everything that you can do with POSIX regex you
> can easily do with PCRE regex, which is faster.
>=20
> It is a decision forever. Do not expect it to come on PHP 5.4 (?) or PHP =
6.
>=20
> Cheers,
>=20
> On Mon, Oct 12, 2009 at 12:46 PM, Mark Krenz <mark@suso.org> wrote:
> >
> > =A0I just found this out a couple days ago when I checked the ereg manu=
al
> > page for something and was shocked. =A0I searched around a bit but
> > couldn't find a straight answer on why this function is being removed?
> > Did the deprecation notice just get made in 5.3 or has it been there
> > longer than that?
> >
> > Thanks,
> > Mark
> >
> > --
> > Mark S. Krenz
> > IT Director
> > Suso Technology Services, Inc.
> > http://suso.org/
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
>=20
>=20
>=20
> --=20
> Guilherme Blanco - Web Developer
> CBC - Certified Bindows Consultant
> Cell Phone: +55 (16) 9215-8480
> MSN: guilhermeblanco@hotmail.com
> URL: http://blog.bisna.com
> S=E3o Paulo - SP/Brazil


--=20
Mark S. Krenz
IT Director
Suso Technology Services, Inc.
http://suso.org/