Re: [RFC] Exceptions in the engine

On Sun, Oct 27, 2013 at 4:51 PM, Nikita Popov <nikita.ppv@gmail.com> wrote: > Yes, my comments are under the assumption that PHP 6 won't be there anytime > soon. Of course, if people suddenly decide that PHP 5.6 should really be > PHP 6, Really not. As of now, we have enough materials for a 5.6 and a 6.x development will most likely take 1-2 years (no, we won't let it go over many years). But 6.x discussions are a bit off topic, except about when should we allow general exceptions usage in the core :) > then there would be little to argue about ^^ Unless we have > *concrete* plans regarding PHP 6 saying "this should go into (a > hypothetical, non-existing) PHP 6" is roughly equivalent to just declining > the feature. > > PHP 6 only makes sense to me if we're planning to actually do changes with > major BC impact. Not things like this RFC, but changes of basic language > semantics (like fixing the 0 == "foo" comparison and other foundational > issues). I disagree here, with both your comment about the relevance of this RFC and what should be a 6.0. I like the idea to move to exception, optionally. But I do not like the idea to have them in one single place, and do not allow them in extensions or other part of the engine. Moving to exceptions usage in the core should be well designed and planed, and globally. This will be something much harder and longer to do than what is proposed here. Cheers, -- Pierre @pierrejoye | http://www.libgd.org