> The big hurry about beta 1 is that it has been lingering for too long and I
> think the only way to push PHP 5 is to finally get a beta out there. We can
> keep on compromising indefinitely because there'll always be that one last
> fix someone wants to do to the PHP 5 codebase and then we'd never get a
> beta out of the door.
> Personally, I don't think this code needs to be in the tree for beta 1.
> From past beta experience we'll probably have another one within a month
> (because ppl will finally be using/debugging our code), so we can put that
> in beta 2.
>
I happen to agree. But I think we should set some sort-of "deadline" on this. Ie, if it doesn't hold up beta 1, then we should have it done by beta 2. How does that sound for a compromise?
We should decide and implement whatever is decided on by beta2.
> So how do we get a formal spec for the changes (starting with nicer names, > i.e. Iterator instead of spl_foreach)? :) It's probably best if you take > Sterling's email and try and come to a final set of interfaces and a very > very short explanation where relevant of what it'll do and then we can > aye/nay each part. >
What's wrong with my interfaces? ;-D
Ugly names? :) I'm not very sure about bringing things like cast overloading into the language space but we can argue about that if/when we have the final list. If you say what you did is final we can start with that.
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
