Re: PEAR Coding Standards
| From: | Clay Loveless | Date: | Mon, 03 May 2004 15:04:03 +0000 |
| Subject: | Re: PEAR Coding Standards | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-28727@lists.php.net to get a copy of this message | ||
On 5/3/04 7:50 AM Pacific Time, Eric Stewart (eric@omicentral.com) wrote:
> I would much rather have a PEAR class return a PEAR_Error when there is
> a problem, than have PHP throw an error. Isn't this the entire reason
> for having an error handling class any way? To allow the programmer to
> decided how to handle errors?
Check out PEAR/ErrorStack.php.
Since we're on the subject of errors and coding standards, seems like it
might be time to update the coding standards to mention that all new
packages should be built using ErrorStack instead of PEAR_Error.
Yes?
BTW -- Greg, correct me if I'm wrong -- but I believe my SVN package is a
good example of using ErrorStack instead of PEAR_Error in a package.
http://www.killersoft.com/packages/example_tree.php
-Clay
--
Killersoft.com