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

Paul Meagher wrote: > > 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 Is there any documentation for the current PEAR modules? Is anyone working on documenting any of the modules, I started using the DB module and at times found myself wondering if i was using it in the 'correct/intended' way. Should documentation be required before a new PEAR module is released with the standard PHP distribution? ---- a side note (personal opinions): I think that when a developer decides to use a PEAR module (is module the correct terminology to use; maybe classes?) they should not be bombarded with a mountain of interdependencies. It makes sense to reuse code between modules but I think that is should be closely watched so that we don't end up with huge classes when in the end the functionality achieved may be rather simple. PEAR should _help_ developers write efficient and maintable code not hurt them by creating large amounts of required source code in order to operate. just my opinion. -ab