Originally posted by Christy Smile:
(1) Do I need to provide JavaDoc for private member variables and private methods?
I agree with Valentin on this. Javadoc everything. As Valentin indicated you can document to any accessibility level, but you may also later determine that a variable or method should be protected instead of private.
Originally posted by Christy Smile:
The Data class provided by Sun did not have JavaDoc for these.
Add the javadocs yourself. The DatabaseException source had no javadoc comments at all. How will it show up in your API documentation if you don't take care of it?
(2) This is not related to JavaDoc though. I have read somewhere that it is good programming practice to avoid using import statements with "*", does this apply to the SCJD? I noticed the source code Sun provides use imports with "*" everywhere.
Valentin is right on this point too, but I don't think you will be penalized if you do this. The reason I say this is that I scored perfect on general considerations (which takes all coding conventions into account) and I used * imports extensively. Some lazy habits are hard to break
Hope this helps,
Michael Morris
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher