Hi,
On Sat, 2009-01-03 at 15:47 +0100, Marcus Boerger wrote:
> > I'd say it would be good to concentrate on making 5.3 stable and then
> > see how new features are accepted. If users really demand such a
> > functionality, when using closures for "real life" development, we can
> > still add it, but that should be done with the time needed to identify
> > side-effects and other consequences, not in a rush during holiday season
> > after a feature freeze has been announced.
>
> Stable also means stable features and semantics. And that includes trying
> to get rid of inconsistencies.
... fixing one inconsistency by introducing new inconsistencies?
Like that one:
<?php
function foo() {}
$foo = "foo"; $foo(); // works
$bar = function(){}; // works
$o->foo = "foo"; $o->foo(); // will not work
$o->bar = function(){}; $o->bar(); // will work
?>
And I fear there will be more. Fixing all of them will take time so we
can delay 5.3 for another half year or so (... oh and during that time
we find another thing to change which will need proper invastigation,
too, so we delay again and then we find ....)
-> We should really try to shorten the release cycle, not making it
longer. Which, for 5.3, means we should concentrate on fixing bugs, not
adding features and change the language.
johannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
