[dev] Horde_Exception in a separate package?

[Michael M Slusarz]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Chuck Hagenbuch <chuck at horde.org>:
>
>> Quoting Gunnar Wrobel <p at rdus.de>:
>>
>> [deletia]
>>> Taking into account that Horde_Framework itself has some  
>>> significant dependencies I would suggest to place Horde_Exception  
>>> into its own package. Would that be okay?
>>
>> We should also make a decision if we're going to standardize on all  
>> of our exceptions descending from Horde_Exception. It makes some  
>> sense, but I've avoided it for a while to avoid too many  
>> dependencies.
>
> Yes, that makes a lot of sense to me. Not necessarily for our own  
> development (though I see some benefits here too), but especially  
> for developers using Horde framework packages for their own projects.
>
>> If we do that, then yes, Horde_Exception should be a separate  
>> package and specifically called out as a dependency anywhere it's  
>> used. If not, then I think we should limit its use further and keep  
>> it in Horde_Core.

I have no problems with moving Horde_Exception to its own package.   
However, I do have strong feelings that all Horde packages should use  
Horde_Exception.  One reason: the ability to do logging within  
Horde_Exception (see, e.g., Horde_Imap_Client_Exception).

michael

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