On 21.06.2009, at 09:51, Lester Caine wrote:
Johannes Schlüter 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,
since many of us probably did not know that 'split' was an ereg
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
add
them to the docs. (See Rasmus's mail) So that this file is as short
as i
makes sense so people have a chance to be aware of as much contents
as
possible - and isn't scared away.
I was probably looking more for pointers to some extra information.
Part of the problem here is that the warnings are being thrown in
code that *I* did not write, so then one either has to search for
updated versions of a library or work out how to fix them yourself -
where I'd 'borrowed' the code originally. Simply hiding E_DEPRECATED
is likely to lead to even bigger blowups later? :(
Actually E_DEPRECATED is only something you should enable temporarily.
Then you can alert either your own team, or the project who's code you
are using and move on. It simply tells you that the code will break
with the next major version. This is not an end of world fatal error.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
