[dev] [commits] Horde branch master updated. 9eaa95c22dd18aec7940206d068fd510b6bda728

[Jan Schneider]

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>>>   Many of these calls can be changed to specifically use Horde_Exception or
>>>   Horde_Exception_Pear; ideally use of Horde_Exception_Wrapped should be
>>>   deprecated and phased out.
>>
>> No, we already discussed this extensively. At least unless we want  
>> to wrap the functionality *inside* Horde_Exception (which isn't  
>> really possible without code duplication until we require PHP 5.3).
>
> Hmm, why? I see a number of places we throw Horde_Exception_Wrapped  
> on something we know is a PEAR_Error object; why not just use  
> Horde_Exception_Pear then?

So that you as the developer don't have to care, what you are  
wrapping. In some places it might be obvious, in others not. But  
really, we discussed this in a long thread already. You should find  
the details in the archive.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/