Re: [revised RFC] PEAR error handling
| From: | Krystof Slaby | Date: | Thu, 28 Aug 2003 23:56:15 +0000 |
| Subject: | Re: [revised RFC] PEAR error handling | ||
| References: | 1 | Groups: | php.pear.dev php.pear.qa |
| Request: | Send a blank email to pear-dev+get-20784@lists.php.net to get a copy of this message | ||
GB> 6. Only errors and exceptions should be returned.
GB> If an error must
GB> terminate the program execution, it is an exception.
What about exception handling?
Exception terminates from program block but doesn't have to terminate whole program when
properly catched.
In php4 language, there are no exceptions of course - but I think this was meant generally.
GB> If an error must
GB> terminate the current function, but not the program execution, it is an
GB> error.
Does 'error code' (non-OK return value) returned from function which was not terminated
mean error?
krysot