On Monday 09 July 2007, chris# wrote: > I will venture to say that the biggest issue was; no transition period. > That is to say that PHP4 and PHP5 are two completely different creatures. > There was no "morphing" period. After several years of working with PHP3/4 > in this fashion, /suddenly/ most of those rules no longer applied (in > PHP5). You've got millions - perhaps billions of lines of code that have to > be nearly completely rewritten to be usable in PHP5. Perhaps a better > solution would be to document an answer to running PHP4, PHP5, and PHP6 on > the same boxen for the most popular OS's. Then there would be little reason > for anyone not to adopt any version(s) of their choosing, and little reason > to complain about an EOL. Seems a sure answer to me.
Better docs on how to run PHP 4 and PHP 5 at the same time would likely be helpful, and someone is working on that for GoPHP5.org, I think. However, your claim that "you have millions... of lines of code that have to be nearly completely rewritten to be usable in PHP 5" is not true. Sure, you could completely rewrite your app, but unless you're doing something very very dependent on objects passing by value porting a PHP 4 app to run correctly in PHP 5 is not the herculean task that some make it out to be. You don't /have/ to rewrite everything to use objects. Even the procedural code is easier, with the extra array manipulation routines. :-) That sounds like more of a marketing issue. -- Larry Garfield AIM: LOLG42 [EMAIL PROTECTED] ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
