On Wed, 19 Nov 2003, Steph wrote:
>> Not to branch the discussion, but again: if we never plan on removing
>> functions, why go to the trouble of deprecating them? Deprecation
>> implies it will be removed.
>>
>
>.. and as Andi said earlier, removal without loud and clear warning will
>break thousands of scripts out there. Making users do something special if
>they want to use their old code, is a much kinder option. It might also
>kick people into updating those scripts before the deprecated functions
>actually die.
I don't really understand how removing a deprecated function
would hurt anyone..doesn't all people test their scripts before
putting new PHP version into production?
Spotting a missing function is quite easy, your script simply
won't work and give a clear error.. :)
Maybe the best way to proceed with deprecation is to first
start giving the error message warning it's deprecated and in
some version remove the functionality and replace the error
with one that says something along the lines of:
"This function is not here anymore, use foobar() instead."
And later remove that too..
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
