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. |