[dev] Dealing with Exceptions (was: Re: [commits] Horde branch master updated. f2b35e73225d8ec7487ef393dc610583fe2b1ece)

[Michael M Slusarz]

Quoting Jan Schneider <jan at horde.org>:

> What I mean with consistency is that all horde exceptions should  
> behave the same way. You may know that Horde_Kolab_Format_Exception  
> is never going to wrap another extension/php error/pear error. But I  
> don't. We have so many libraries, each using its own exception  
> class, and I don't want do look up each exception's class definition  
> to see how I have to use it, when I'm going to fix/code something in  
> some arbitrary library. I want to be sure that any Horde exception  
> class is working the same, so I can wrap it around any of the  
> errors/exceptions that might occur during PHP development.

Agreed.  I am willing/able/expecting to learn the API for the  
Horde-wide Exception class.  I do not need/want to have to look up the  
api for individual packages distributed with Horde.

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]