>Kind of the coding standard we agreed upon (off the top of my head) as a
>group was:
>
>1. all public and protected functions must have javadoc
>2. all subprojects must have at least a how-to and some sample code
>explaining their basic use.
>3. stuff must compile
>4. the build must work
+1
I'd like classes and packages to have javadoc, too. This would give
developers a broader view than the method docs' peephole view while
still being more detailed than HOWTO and sample code. Does that
sound reasonable? Perhaps we should *encourage* it, but not
*require* it.
Best regards
Rainer Klute
RAINER KLUTE IT-CONSULTING
Dipl.-Inform.
Rainer Klute E-Mail: [EMAIL PROTECTED]
K�rner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
