On Thu, Jul 16, 2015 at 4:58 AM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote:
> I understand many of us dislike INI switch nor runtime switch that changes > behavior. However, it's impossible to move to exception at once because we > have no control for users' code including 3rd party modules. Well, ini settiing remains ugly. Code will have to take care of it and this is not going to be a good thing. > IMHO. Rather than adding exception adopted functions gradually, having the > switch > is better for in the long run. We may deprecate/remove the switch 10 years > later or more. > > BTW, I'm thinking to have > "ModulenameException"/"ModulenameFunctionException" > or like rather than simply calling/converting errors to ErrorException when > exception > is enabled for functions. I am not sure I like this idea. I would prefer to define namespace and rely on standard names (when possible) and per extension namespace instead. I also agree to actually deal with exceptions globally at once instead of incremental additions in more or less random places, functions or methods. Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
