Thomas Goyne wrote:
On Tue, 15 Jun 2004 14:46:01 -0400, Jason Garber <[EMAIL PROTECTED]> wrote:
[snip]
I would say that the priority on developing PHP is:
1. Bug Fixes from bugs.php.net
2. Features that are slated for upcoming versions of PHP
3. Recoding old functions to make them faster and more stable where needed.
As a user, I personally see placing new features over making old features work better a large mistake. Perhaps that was necessary back in the days of PHP3, but its been a very long time since I've run into simply not being able to do something. Quite often, however, I've run into that the most direct way of getting something done performs too poorly to be usable. Maybe I'm just stuck with worse hardware than most others, but improved performance is one of the biggest thing I'd like to see out of new releases.
On the other hand, if code IS working stably then it may be better to leave it alone. I'm not saying don't tidy up code, but ALL the tests against a change need to be in place before a change is applied to the live code, and in some cases it is worth remembering that PHP *IS* multi-platform. Some changes tailored for one environment may be a disaster in another - code for the 'safe' ground.
So changes must be applied properly, tested in all ports and approved before going live. At present we are in the final stages of release for PHP5 - which I want now - so we do not want to introduce updates that take us back to the start of testing :)
Once PHP5 is out - THEN the sorts of fixes Alexander is suggesting could be looked at - but not until then.
The next question is - are both PHP4 and PHP5 going to be run in parallel, like Apache 1 and 2 so that neither gets finished ;)
-- Lester Caine ----------------------------- L.S.Caine Electronic Services
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
