Re: Re: [PEPr] Comment on PHP::Autoloader
| From: | Markus Malkusch | Date: | Fri, 28 May 2010 17:16:00 +0000 |
| Subject: | Re: Re: [PEPr] Comment on PHP::Autoloader | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-53515@lists.php.net to get a copy of this message | ||
Paul M Jones:
> Your work, while useful for non-standard naming, is probably not something
> I'd like to see in PEAR. In my opinion, PEAR ought to enforce its own
> standards as much as possible.
I agree to follow conventions. And there is no question about following these
conventions in PEAR itself.
PEAR is a class library, which is intented to be used *outside* of PEAR. I
don't see much sense in offering an Autoloader for application developers who
must follow the convention of the class library. I want to be clearly
understood, that the autoloader should not do the autoloading inside of PEAR
(although it could). Its purpose is beeing used as a component by any
developer. There exists enough reasons to define classes outside of the PEAR
conventions.
Of course there is no need to avoid the PEAR convention. The autoloader does
work well with them. But I don't really think that a class library should
educate its users.
Markus Malkusch