beware, troll. Tyrael
On Thu, Dec 31, 2009 at 11:11 AM, mm w <0xcafef...@gmail.com> wrote: > Those things were already deprecated, it's good thing that php 5.3 > finally broke bad code, php 5 (since the first alpha) is there since a > while, drupal is drupal if folks don't want to fix it, what's the big > deal there? just pach it yourself it's open source isn't it? so > nothing stop you to fork, what's the matter with the language > implementation internal-list seriously drupal I don't care, drupal is > not php and won't decide for keeping legacy support or not, so > complain to drupal team not here > > On Thu, Dec 31, 2009 at 1:04 AM, Stanislav Malyshev <s...@zend.com> wrote: >> Hi! >> >>> The PHP 5.3 compatibility issue for the Drupal CMS >>> (http://drupal.org/node/360605), for example, had over 200 comments, and >>> it took about 9 months before a patch was committed to the current >>> version of Drupal in September (see comment 158). That's not the only >>> example, but it's a prominent one that comes to my mind. >> >> it looks like their issues were primarily caused by: >> 1. Relying on exact text of error messages >> 2. Using runtime by-ref passing (which one definitely shouldn't do) >> >> -- >> Stanislav Malyshev, Zend Software Architect >> s...@zend.com http://www.zend.com/ >> (408)253-8829 MSN: s...@zend.com >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
