Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes Documentations Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "Documentations" Watch "Documentations" New topic


Payal Shah
Ranch Hand

Joined: Jul 10, 2006
Posts: 67
I have the following questions about docuemtnations:

2) I am using Microsoft's wordpad for my documentation. Not using Notepad. Just want to double check that wordpad is ok to use.

3)I am generating javadoc for public access level modifiers only. The requirement does not say anything about it.

thank you.
Alecsandru Cocarla
Ranch Hand

Joined: Feb 29, 2008
Posts: 158
1) I have no idea. It's probably something that the text file processors that SUN uses understands.

2) You should be safe as long as the text files you generate with wordpad are viewable with notepad and any other simple textfile editor. Why don't you use the IDE for writing the choices file?

3) You should at least provide javadoc for protected and package access level methods. Everything that another programmer which uses your jar can see should be documented. Some people around here even provided javadoc for private methods. Maybe you should search around a little before asking.

SCJP 1.4 100%
SCJD 99.5%
Cless Alvein
Ranch Hand

Joined: Jun 18, 2007
Posts: 39
Also, I did not put this in my choices.txt but I did document private members (especially private inner classes) on the basis that if they were refactored out and made visible, then the documentation would already be there. Plus, more documentation makes it easier for the hypothetical "junior programmer" to read.
I agree. Here's the link:
subject: Documentations
It's not a secret anymore!