Howard and Mike,
I went through and added skeletal phpdoc comments in as many main libs and classes as I had time to with the hope that developers would see the format and choose to expand the comments that have todo tags and add comments to new functions as added. As you add new functions or make edits to a function please add or expand on existing phpdoc comments.
I've added a guidelines document to cvs contrib, your feedback is welcome:
cvs:/contrib/php_doc_guidelines/moodle-phpdoc-guidelines.html
I went through and added skeletal phpdoc comments in as many main libs and classes as I had time to with the hope that developers would see the format and choose to expand the comments that have todo tags and add comments to new functions as added. As you add new functions or make edits to a function please add or expand on existing phpdoc comments.
I've added a guidelines document to cvs contrib, your feedback is welcome:
cvs:/contrib/php_doc_guidelines/moodle-phpdoc-guidelines.html
I've posted phpdoc output from a full run against the entire Moodle 1.6dev code. Developers, here is an example as to why you should be including good phpdoc comments for every new function, define, class and file and why you should be updating the comments on functions as you use them.
http://moodle.sourceforge.net/dhawes-phpdoc
http://moodle.sourceforge.net/dhawes-phpdoc