You may not be running on PHP 5, but some of us are or will be soon. That means if you code non-PHP 5 code, we can't use your code. Web hosts will eventually upgrade to PHP 5, be it next month or next year, and Drupal WILL, sooner or later, have to be 100% PHP 5 friendly. The more PHP5-incompatibility you code now, the more time you'll spend fixing it all later. Whether later is December 2005 or December 2007, you'll still have to go back and fix it. Develop under PHP 5 E_STRICT | E_ALL. Make the system nitpicky. Fix everything it complains about. That way whenever people DO start migrating to PHP 5 en masse, Drupal is already there. That makes it something people migrate TO, instead of away FROM, when they find their old web apps don't work on PHP 5 anymore. Do you really want people to get upgraded to PHP 5 and find "Oh, Drupal doesn't work anymore. I guess I'll have to dump it and switch to Typo3"? I'd rather they face the opposite situation. :-) On Friday 14 October 2005 04:17 am, Karoly Negyesi wrote:
Hi!
PHP 5.0.5 broke Drupal 4.6 (reference is now an error).
Reading http://shiflett.org/archive/150 this, I can not care less and I am not likely to put any efforts into making Drupal PHP5 compatible. If my code is PHP5 compatible, fine, but I will not bother myself. (This does not mean slopy code, $_POST['op'] which results in notices is acceptable)
I think I'll wait another year before looking again.
Opinions, please.
Regards
NK
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com 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