On Sun, 2003-03-23 at 10:33, Wez Furlong wrote:
> We need to do at least one of the following:
>
> 1) Force all exceptions to be descendants of a builtin Exception class
> 2) Force all exceptions to implement a Throwable interface
> 3) Provide a catch-all syntax to the language for exception handling.
>
> This is *extremely* important for people writing such things as SOAP or
> RPC servers that want to keep their implementations as robust as
> possible.
>
> While we are at it, lets have the call to undefined method fatal error
> and the type-hint checking raise exceptions too; procedural code will
> still bail out if it doesn't catch the exception, while robust OO coders
> will be able to act on the event and handle it gracefully.
As mentioned over IRC.
Why do this with Throwable (which raises the WTF factor), why not just
add a generic default case:
try {
throw new Bar;
} catch ($e) {
// do stuff with the exception
}
sure introspection will suffer, but I'm against anything that forces a
developer into a contract they may not want to make.
-Sterling
--
"Science is like sex: sometimes something useful comes out,
but that is not the reason we are doing it."
- Richard Feynman
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
