Re: Re: cvs: php4 /pear Mail.php /pear/Mail rfc822.php

Hi Chuck, > > Whatever coding standard we come up with, I think it should try to take the > > best ideas from these three major code repositories of quality code. > > Okay. What are the best ideas from PHPlib and the classes repository? I'm not > aware of any standards associated with the classes repository, and I'd moved > away from phplib even before I found PEAR because I thought I could do things > better. So get down to specifics: what do you like about phplib that you want > to see in PEAR? > How is this for starters? From PHPLIB - Excellent documentation - Integrated development library. You can access a range of commonly used libaries for backend development: Auth, DB, Sessions, Templates, and Form classes. - An attempt was made to make a lightweight core with optional extensions - Sample applications shipped with the library indicate how to use it From PHPClasses - Easy for contributors to add and update code without learning CVS - Capability of tracking download popularity for different classes (nice ego boost for developers) - The main dude is also the most active contributor BTW, is anyone working on an Authentication class? Would such a class be required to use PEAR's database abstraction layer (because it would involve access to a database)? I would like to see something like a PHPLIB auth class (in terms of supported methods) in PEAR but with a cleaner implementation (not so many nested case statements). Is anybody currently working on an Auth class for PEAR? Regards, Paul Meagher