On Fri, Aug 21, 2015 at 3:52 AM, Pierre Joye <pierre....@gmail.com> wrote: > On Fri, Aug 21, 2015 at 9:38 AM, Scott Arciszewski <sc...@paragonie.com> > wrote: >> On Wed, Aug 19, 2015 at 11:36 AM, Trevor Suarez <ric...@gmail.com> wrote: >>> Ah, I didn't realize this thread existed. I had just commented on the old >>> one, but the point still stands: >>> >>> PHP 7.0 RC1 was just tagged. >>> Shouldn't this be a relatively high priority to fix/decide so we don't end >>> up with behavior that can't be fixed until PHP 8.0? >>> >>> On Mon, Aug 10, 2015 at 6:54 PM Niklas Keller <m...@kelunik.com> wrote: >>>> >>>> > >>>> > Okay, great, we have people on both sides on this discussion. I hope >>>> > nobody minds if I sit this part out. >>>> > >>>> > What specifics need to be discussed? Should somebody set up a poll? (I >>>> > don't know how to do that.) >>>> >>>> >>>> You can find information on how to setup a poll in step 6 here: >>>> https://wiki.php.net/rfc/howto >>>> >>>> Regards, Niklas >> >> I agree that this should be a relatively high priority. I'm not sure >> what the next steps would be. (Aside: I still have a PR I need to >> write that I've been holding off on until the fate of PHP 7's CSPRNG >> feature is determined.) >> >> Can we reach some sort of consensus on throw new Exception vs throw new >> Error? > > I think the best would be a RFC, not only for the decision itself but > also to have a clear view about what will be changed or affected. > > Cheers, > -- > Pierre > > @pierrejoye | http://www.libgd.org
Fine, let's do this: 1. Violate the feature freeze for this exceptional decision. 2. One of the folks in the camp that WANTS an RFC and a drawn out formal decision-making process opens it with a poll. 3. Give me voting karma. Let's NOT make the CSPRNG feature fail open. That is an absolutely terrible idea. Scott Arciszewski Chief Development Officer Paragon Initiative Enterprises <https://paragonie.com> -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php