[PEPr] +1 for RFC::Error Handling Guidelines for PHP5 packages
| From: | PEPr | Date: | Tue, 24 Aug 2004 18:02:12 +0000 |
| Subject: | [PEPr] +1 for RFC::Error Handling Guidelines for PHP5 packages | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-32910@lists.php.net to get a copy of this message | ||
David Costa (http://pear.php.net/user/gurugeek) has voted +1 on the proposal for RFC::Error
Handling Guidelines for PHP5 packages.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=132
Vote information:
http://pear.php.net/pepr/pepr-vote-show.php?id=132&handle=gurugeek
Comment:
I have been using a prototype of PEAR_Exceptions in two new PHP 5 packages (DB_Sqlite_Tools is
already in CVS) and I think it is fairly easy to get familiar with PEAR_Exception and use them
properly. In a professional solution you can for instance have a database logger which throws an
exception and decide to catch and and continue the normal execution of the code if there is a db
error (e.g. an Sqlite lock on a db file) so I am all for using the PHP 5 functionality at its best.
Existing solution for PHP 4 packages are excellent but we can't just use PHP 5 in the way we
used PHP 4, at least I don't find this to be a contructive approach. There are new features and
a new way of thinking around our code, let's take advantage of it.
--
Sent by PEPr, the automatic proposal system at http://pear.php.net