Hi Scott, > -----Original Message----- > From: Scott Arciszewski [mailto:[email protected]] > Sent: Monday, July 27, 2015 8:58 AM > To: Anatol Belski <[email protected]> > Cc: Aaron Piotrowski <[email protected]>; Sammy Kaye Powers > <[email protected]>; Larry Garfield <[email protected]>; Jakub Kubíček > <[email protected]>; Stanislav Malyshev <[email protected]>; > [email protected]; Pierre Joye <[email protected]>; Dean > Eigenmann <[email protected]>; Yasuo Ohgaki > <[email protected]>; PHP Internals <[email protected]> > Subject: Re: [PHP-DEV] Core functions throwing exceptions in PHP7 > > My only concern is that, we have a fixed timetable for the 7.0.0 release. It's > certainly a good idea to develop a cogent strategy before moving forward, but > I > worry that bikeshedding will get involved and we won't make the deadline. > Clear, it is not something arising overnight. And bikeshedding is good because it reveals many potential issues. Clear, it needs time. RC1 might come after beta3 (or might not) which is roughly 1 month from now on. It is in your guys hands.
> I propose that, if a better strategy cannot be presented in time for RC1, > consistency should take a back seat to security. Fail hard, throw an Error, > deal > with the details later. Clear, it can't be complete and accepted/declined in such a short period (though much time is lost discussing only this one case). That's why I wrote literally about a "rough draft". But it also can't arise if no one cares. Then yes - we end up in a situation like "A over B" or "B over C" without really knowing the consequences. Cheers Anatol -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
