Hi Joe, On Sat, Nov 19, 2016 at 12:28 AM, Joe Watkins <pthre...@pthreads.org> wrote: > I think most people would be happy to provide a reason, if you have it > listed. > It should be listed, because it should have been brought up during > discussion. > > Obviously we don't live in an ideal world, and you may get lots of no votes > still that don't provide a reason.
There are clear cases that people misunderstand proposals. Recent example is PRNG adoption for uniqid(). I proposed patch does not have any BC, but there were people opposed based on false FUD. i.e. RPNG device access causes access error which is _nothing_ to do with internal function. Another example is session ID validation. It is mandatory to keep session as secure as possible, yet there are some people do not realize(?) why it is mandatory. There is workaround, but I haven't seen implementation does it correctly. I would rather just fix the issue rather than trying to teach how to do it. Anyway, regardless of opposition is reasonable or not, disclosing the reason why it is not preferred is valuable. Could you at least state in the RFC that all voters who are not in favor of the proposal should disclose the reason? Regards, -- Yasuo Ohgaki yohg...@ohgaki.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
