Zeev, >> Then that's great! But let's find that out by voting rather than guessing, >> and >> rather than politicking. Let's let two competing proposals go head to >> head. > > I'd rather find out by first discussing the alternative, rather than just > moving ahead to a revote - especially a revote that was placed on a > shortened timeline - given the importance of this RFC. But as you clearly > disagree, it's your call to make and I respect that.
With all due respect, we've been discussing this for literally 5 years since Ilia's commit into 5.4 was reverted: http://marc.info/?l=php-internals&m=127454069030304&w=2 I've personally gone through several iterations of it including associated discussion. For this proposal (v0.5), I think the time for fundamental behavior discussion is over. Some disagree, sure. But we've never required 100% consensus before, why start now? I am asking for discussion on the finer points. And indeed some minor modifications have been made. And I'm open to making them. Hence why I specifically asked in the announcement on list that if people disagree they should explain why (**from a technical level**). I personally don't see how a new proposal can fit better than this one, hence why I am moving forward with it. Show me, in writing, in an RFC, how your proposal is better, and I'll gladly withdraw (or delay) this proposal. But short of that, I don't think it's fair to say "first discussing the alternative". This topic has been discussed to death in circles over the past several years. You're involved now. Awesome. Show me why your proposal is better rather than trying to just tell me to stop or pause. Show the result of the discussion. Thanks Anthony -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
