Re: Class constructor behaviour
On 17 January 2015 at 16:04, Rowan Collins <[email protected]> wrote:
> The difference is that AFAIK all the exceptions returned by OOP extensions right now are of
> classes specific to that extension, whereas this would be a global engine-thrown exception.
Sorry - I wasn't clear. I didn't mean they should throw generic
exceptions; they definitely should throw exceptions specific to the
code being called. To a very large part these exceptions already
exist:
The intl extension has: http://php.net/manual/en/class.intlexception.php
The reflection extension has:
http://php.net/manual/en/class.reflectionexception.php
For the intl extension, these are already in use in some places, if
the user has set "intl.use_exceptions".
This is why I think most, if not all, of the work would need to be
done before an RFC could be voted on - it's one of those cases where
people could disagree with details of the RFC, even if they agreed in
the general idea.
cheers
Dan
Thread (19 messages)