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. --Wez. On Sun, 23 Mar 2003, Sterling Hughes wrote: > On Sun, 2003-03-23 at 10:24, Stanislav Malyshev wrote: > > SB>> The lack of a common interface of thrown exceptions hinders the > > SB>> development of applications like PHPUnit that need to be able to > > SB>> work with *every* possible exception. > > > > Don't we have a way to catch any exception in the language yet? > > > > If you want to catch any exception, just require people to define their > exceptions as extending the "exception" class, if they wish to use > phpunit. We shouldn't have an engine-level straightjacket on exceptions > (more of a response to sebastian's mail than to stas'). -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
