Stanislav Malyshev wrote:
> try {
> } catch($e) {
> }
>
> where $e would catch any exception.
This would even be constistent with the other class type hints.
I could live with that,
Sebastian
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
SH>> phpunit. We shouldn't have an engine-level straightjacket on
SH>> exceptions (more of a response to sebastian's mail than to stas').
I meant something more to the lines of:
try {
} catch($e) {
}
where $e would catch any exception.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL P
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 handl
At 16:33 23.03.2003, 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.
Coming from a
Marcus Börger wrote:
For me it sounds like Sebastian wants to write only one catch
handler but that's not the point of designing with exceptions.
No, that's not what I have in mind.
The following is from PHPUnit/TestCase.php
try {
$this->runTest();
}
catch (AssertionFailedEr
Wez Furlong wrote:
> This is *extremely* important for people writing such things as
> SOAP or RPC servers that want to keep their implementations as
> robust as possible.
I was thinking about those, too.
> While we are at it, lets have the call to undefined method fatal
> error and the type-hi
At 16:24 23.03.2003, 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?
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 suc
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
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?
--
Stanislav Malyshev, Zend Products Enginee
10 matches
Mail list logo
