To read all comments associated with this story, please click here.
There's actually a lot of things they could have had trouble with in moving to PHP5. I imagine their scripts weren't very extensive.
I am just finishing moving my companies code to work with PHP5 from PHP4 (and with register_globals off...
). It actually wasn't too damn. A few instances of domxml. Some issues with implementation of the __call method (it differs between 4 and 5 yet that isnt documented), nusoap (named soapclient), etc.
The real bitch was fixing the code to work with register_globals off (and error_reporting set to E_ALL for most of the code).
We're developing a new platform now though and it's going to be developed strictly on PHP5 with E_STRICT on. Thank god.
The good thing about this is all the work we get paid to do. First they paid us for writing systems in <PHP4, then they paid us for maintaining them, and then for migrating them to PHP4, and now we get paid to migrate their systems to PHP5
... aaahh the miracle of the never ending software upgrade cycle 






Member since:
2005-07-06
Running both versions is imho unwanted. This makes people lazy for taking steps to migrate. It's known for more then one year that php4 will be ended this year.
We migrated all our customers to PHP 5 last year. And we gave customers one year time to migrate there scripts. And btw of the 15.000 customers of us only 50 people had problems with PHP 5. Mostly because they were using this *EXPERIMENTAL* dom-xml stuff.