On 15/02/2015 22:15, Andrea Faulds wrote:
It might be for the best that we don’t keep it in voting. During the voting process, it became apparent that the declare() syntax (with all its idiosyncrasies) was a big problem (influencing at least 3 people’s votes), so much so that I decided that I’d make a follow-up RFC to fix it after voting ended, to avoid having to cancel the vote. Now that voting’s cancelled, that could be fixed properly if someone revived the RFC.
People voting one way or another, or their reasons for voting, should never be a reason to stop a vote, particularly one that has been going for so long, and received so many votes. That way, madness lies, because someone could keep closing and reopening different versions of a vote, and people whose vote was not influenced by that factor would have to keep remembering to re-register their unchanged vote.
If the vote fails, we know that some people may be persuaded to vote differently (in either direction) on a similar proposal with different syntax; if it passes, there is nothing to stop another vote defining a different syntax before 7.0 is released.
I think the vote totals still make a statement. The vote may have ended 4 days early, but it’s only 1 vote short of a 2/3 majority.
That's why I think it should continue; so that that statement is not open to argument. Right now, anyone who disagrees with the result can simply say "well, it was closed early, so it's meaningless".
Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
