Re: Services_Yadis: get rid of PEAR dependency
| From: | till | Date: | Thu, 17 Jun 2010 16:58:05 +0000 |
| Subject: | Re: Services_Yadis: get rid of PEAR dependency | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-53576@lists.php.net to get a copy of this message | ||
Can anyone of the PEAR(2) overlords update the RFC accordingly?
http://wiki.pear.php.net/index.php/PEAR2_Exception_Policy#Proposed_Changes:Base_Exception_interface
... or maybe that's not the most recent one?
Till
On Wed, Jun 9, 2010 at 3:25 PM, Ken Guest <kguest@php.net> wrote:
> I'm not an aol-er but, I agree - especially if it makes transitioning
> packages for PEAR2 easier.
>
> k.
>
> On Wed, Jun 9, 2010 at 2:01 PM, David Coallier <davidc@php.net> wrote:
>>
>> I'm for it as well as I don't see how it breaks the coding standards
>> and makes the packages PEAR2-ready.
>>
>> On 9 June 2010 13:33, Brett Bieber <brett.bieber@gmail.com> wrote:
>> > On Wed, Jun 9, 2010 at 7:17 AM, till <till@php.net> wrote:
>> >> On Fri, Jun 4, 2010 at 10:49 PM, David Coallier <davidc@php.net> wrote:
>> >>> On 4 June 2010 18:04, Bill Shupp <hostmaster@shupp.org> wrote:
>> >>>> Yeah, that's why it's there. The exceptions extend
>> >>>> PEAR_Exception,
>> >>>> per the requirements. I don't mind removing the parent class of
>> >>>> PEAR_Exception, as I'm pretty sure no one is catching that.
>> >>>>
>> >>>
>> >>> While you are at it, what you could do is try to have native
>> >>> exceptions that follow what kind of exceptions they are expressing and
>> >>> this way it would make the package more PEAR2-ready :)
>> >>
>> >> Is that "allowed" in PEAR1 too? Just curious if a decision was
>> >> reached...
>> >
>> > I'm completely for it.
>> >
>> > --
>> > Brett Bieber
>> >
>>
>>
>>
>> --
>> David Coallier
>>
>> --
>> PEAR Development Mailing List (http://pear.php.net/)
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>
>
>
> --
> http://blogs.linux.ie/kenguest/
>