Re: Please reconsider supporting PHP 5.2

Am 25.07.2010 11:17, schrieb Karoly Negyesi: > This is a very interesting decision as 5.3.0, compatibility wise, is a > major release. I always felt it was PHP 6.0 but it was not called so > because there was a development branched called that (which was later > abandoned). This is simply not true A clean designed application has to run the whole time with error_reporting = E_ALL | E_STRICT and so you should have seen the problems long ago > This broke Drupal 6 big time and while core has been fixed, contrib is > a bit slower to adapt. Previously, it was possible to pass in simply > NULL if you did not care about the by-reference argument. The problem is that the developers of drupal, joomla, wordpress are not working error_reporting = E_ALL | E_STRICT as i do since teh first day i use php even on production servers While 122 installations of our own software throwing up to 10 warnings a month many other software rides a DOS-attack against mysql if rsyslog is using a database > Also, the deprecation of ereg will affect Drupal 6 over its lifetime > as the module install / enable functionality uses ereg in a way that > can't be fixed: as it is not on a performance critical code path noone > bothered to rewrite the truly ancient directory scanning function > which takes an ereg as it's argument earlier. And we can't break APIs > in a minor release so this can only change in Drupal 7 which is poised > to be released in a few months. Seems that you do not understand what deprecated means? See that such calls are using a @ before to not make crazy peopole like me with thousands of warnings and you have time enough to clean your code > Then there is the date_default_timezone_set / date.timezone snafu. If this is a problem the sysadmin did not his job date.timezone = "Europe/Vienna" in php.ini exists since years an dshould be set in all clan server setups

Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc