You are here: Re: Breaking backwards compatibility - good or bad? « PHP Programming Language « IT news, forums, messages
Re: Breaking backwards compatibility - good or bad?

Posted by Wayne on 12/21/05 02:17

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!!

 

Navigation:

[Reply to this message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация