Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44384
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: PHP internals <internals@lists.php.net>
Message-ID: <0A98F482-ADE6-40C6-B62A-D9FD51B54AA8@pooteeweet.org>
To: Lester Caine <lester@lsces.co.uk>
In-Reply-To: <4A3DE678.90706@lsces.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 21 Jun 2009 10:10:57 +0200
References: <2F881AF5-845A-4CCD-8D9F-31D99C383C6F@pooteeweet.org>	 <4A3C8687.5090804@lsces.co.uk> <1245541002.6521.22.camel@goldfinger.johannes.nop> <4A3DE678.90706@lsces.co.uk>
Subject: Re: [PHP-DEV] PHP 5.3.0RC4
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 21.06.2009, at 09:51, Lester Caine wrote:

> Johannes Schl=FCter wrote:
>> On Sat, 2009-06-20 at 07:49 +0100, Lester Caine wrote:
>>> While I know that ...
>>> - All ereg functions are deprecated and emit E_DEPRECATED errors.
>>>   Use PCRE (preg_*()) instead.
>>>
>>> ... is accurate, I think a little more detail would help here, =20
>>> since many of us probably did not know that 'split' was an ereg =20
>>> function - for instance?
>> hm, the las version on the wiki listed them ...
>> In general: I'd like if people could come up with more details and =20=

>> add
>> them to the docs. (See Rasmus's mail) So that this file is as short =20=

>> as i
>> makes sense so people have a chance to be aware of as much contents =20=

>> as
>> possible - and isn't scared away.
>
> I was probably looking more for pointers to some extra information. =20=

> Part of the problem here is that the warnings are being thrown in =20
> code that *I* did not write, so then one either has to search for =20
> updated versions of a library or work out how to fix them yourself - =20=

> where I'd 'borrowed' the code originally. Simply hiding E_DEPRECATED =20=

> is likely to lead to even bigger blowups later? :(


Actually E_DEPRECATED is only something you should enable temporarily. =20=

Then you can alert either your own team, or the project who's code you =20=

are using and move on. It simply tells you that the code will break =20
with the next major version. This is not an end of world fatal error.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org