On Sat, 2007-08-25 at 10:33 -0400, Nathan Nobbe wrote: > yes, i agree, people wont be all-of-a-sudden ignoring php4, but the > notice on php.net says to migrate apps to 5 through the rest of the > yaer. id say thats ample time to move away from it. Migrate doesn't necessarily mean ditching PHP4 compatibility. It means ensuring you are PHP5 compatible. That's reasonable. > pretty much all of my applications rely on php5 features except those > where the system was running on php4 when i arrived. and then i > have to rely upon contriving mechanisms that are already integrated > into 5. > plus i place comments where i could be placing keywords. the success > of an application using objects in php4 relies heavily on > communitcdation > w/in the team, whereas w/ php5 the communication can occur w/in the > code > using keywords. > > im sure php4 applications can be very robust, but why bother rewriting > things > that are available at the language level as they are in 5; and praying > that > someone doesnt call a method because they didnt bother to read the > comments.. Rewriting? You're assuming developers of PHP4 are using all of the features in PHP5 but written using PHP4 code. That's not a very valid assumption. You're also assuming they didn't already have code written in PHP4 that was then duplicated b internal code in PHP5. Hell, many PHP4 AND PHP5 developers don't even use OOP. Tell me what is compelling in PHP5 that doesn't rely on you being an OOP developer? Exceptions don't count since that's an individual bent. C has no exceptions and it gets on fine (PHP is written in it :) Cheers, Rob. -- ........................................................... SwarmBuy.com - http://www.swarmbuy.com Leveraging the buying power of the masses! ........................................................... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
