Hi ya old fella,

Going there, i write first:

the method name, a quick summary of the javadoc of the main public method,
then my unit tests that follow the sequence of ideas described in the
javadoc, then i implement the last method called and go up to the public
method.
i then write the javadoc for all the small methods once all test cases are
green, a recent example would be here:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/raccoon/raccoon-core/src/racc
oon/tools/generator/tibRepo/RaccoonToRepo.java

I documented the method raccoonToRepo and used extensively the refactoring
tool of IDEA, and ended up javadoc'ng the private methods. :o)

a++ Cedric


_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features

Reply via email to