Re: RFC: PEAR Changes / Scope

On Sun, 11 Nov 2001, Lux wrote: > > So we will not allow complete applications even in EXT? > There's already freshmeat, hotscripts, and the like for that. Extending > PEAR into that arena as well would probably be too far from the original > focus, I would say. But a set of applictions, following specific coding standards would be great. That's the big advantage of PEAR. Most of the classes on phpclasses.upperdesign.com are better implemented and better documented. But all of them are coded in a completly different way. I dislike that, because it's difficult to change the code in this case. Always remember PEAR stands for PHP Extension and _Application_ Repository. Regards, Sebastian Nohn -- NeT&Trade GmbH email : s.nohn@nettrade.de TechnoPark der GMD www : http://www.nettrade.de/ Rathausallee 10 tel : +49 22 41 - 20 40 33 53757 Sankt Augustin fax : +49 22 41 - 20 40 34 Germany mobile: +49 173 - 5 96 43 77