Posted by Jerry Stuckle on 12/21/05 05:31

Wayne wrote:
> On 20 Dec 2005 23:53:00 GMT, "Default User" <defaultuserbr@yahoo.com>
> wrote:
>
>
>>If you deprecate something, and no one cares, then it can be removed
>>quickly. On the other hand, if it will have a huge affect, then it's
>>smart to wait and see.
>
>
> Of course, given that PHP issues a warning (under E_STRICT) for
> depreciated elements the effect is pretty huge always. Unlike
> compiled languages like C/C++ were the warning exists only at compile
> time, PHP warnings have a much bigger effect.
>
>
>>How much time? THAT is the question. There are some deprecated elements
>>in C and C++ that expect will outlive me.
>
>
> PHP should move at a much faster pace than C/C++. There are
> significant differences between the platforms, the applications, and
> the environments that they aren't entirely comparable. Since PHP5
> breaks so much backwards compatibility anyway I don't think
> depreciated elements should stick around as long -- it's not as if you
> have as much legacy code around that is running that is not already
> being modified.
>
> PHP also has way more mistakes in it than, for example C/C++, that
> should be corrected. PHP started out as a big ball of hacks!!
>

Wayne,

I agree with you. Deprecated elements should be removed eventually. Not
necessarily the next release, but they shouldn't be kept around forever,
either.

And if Default User needs the function that badly, he can always
recreate it. Most deprecated functions can be recreated with other PHP
code. And if it can't, he can always go back to the previous version's
PHP source and compile that section of the code into the new PHP version
(or at least something which does the same). A definite advantage of
having the source!

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[Back to original message]