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

Quoting Aaron Bush <abush@microcenter.com>: > Is there any documentation for the current PEAR modules? The inline PHPDoc documentation. > 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. Well, the list is here for questions. > Should documentation be required before a new PEAR module is released > with the standard PHP distribution? I think that it would be a good idea to require inline documentation. > 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. Is there anything particular you have in mind here? Obviously we should avoid dependencies if possible, but building larger pieces out of smaller components is a great way to build up robust, complex applications. -chuck -- Charles Hagenbuch, <chuck@horde.org> "If you can't stand the heat, get out of the chicken!" - Baby Blues