> The advantage of maintaining reverse compatibility is that it helps encourage
> people to upgrade. Many more people would have many more concerns if the
> 4 -> 5 upgrade broke programs using depreciated practices.
Well, that's the thing I don't get. If I have working system for PHP 4 engine, why would I want to _upgrade_ (i.e. switch) to PHP 5 engine? Would it not be more compelling for me to have 4 and 5 as separate Apache modules or something like that? Interoperability problem could be solved by some kind of inter-version bridge (like PHP/Java integration module). A the same time, this would free PHP developers from BC.
> I will be honest, I've written the majority of my code in the last
> year, but am I
> 100% positive that I'm not using anything that was marked as depreciated in
> PHP 4? Absolutely not. For all I know I might be using some deprecated function
> in some arcane, rarely used administrative include file hiding somewhere in the
> depths of my file system. Everything would apparently keep working when I
> upgraded, and even for days/weeks after the fact. Then boom, one day something
> important brakes, and I have no idea why.
Look at your situation from different perspective. Wouldn't it be nice to be absolutely sure that your website does not uses any deprecated code? You would most certainly know that if PHP 3 and PHP 4 would be handled by different engines.
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
