|
||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||
java.lang.ObjectUsingJavadoc
public class UsingJavadoc
This class is a demo of javadoc.
This comment will go at the top with the name of the class.
To javadoc this file while creating a tech spec, try
javadoc -private UsingJavadoc.java
| Field Summary | |
|---|---|
private int |
x
the integer x. this top part will go in the field summary. |
int |
y
the integer y |
| Constructor Summary | |
|---|---|
UsingJavadoc()
the default constructor. |
|
| Method Summary | |
|---|---|
void |
moreOnJavadoc()
Other commands you can give javadoc. |
int |
someMethod(int p)
purpose: this is an example of what Javadoc can do These lines go into the method summary. |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Field Detail |
|---|
private int x
public int y
| Constructor Detail |
|---|
public UsingJavadoc()
| Method Detail |
|---|
public int someMethod(int p)
p - this is my parameter...
code or pseudo code goes in tags like these
Notice that the previous words appear in a different font.
other html tags such as
for paragraph work too. Notice that a new paragraph started in the Javadoc. If you know other html tags, you can experiment with them.
Don't use too many html tags tho since it makes the Java harder to read
precondition: not a whole lot
postcondition: something i'm sure
There are html tags which render lines as-is. These may also help with pseudo code.
this is being shown exactly as typed
even the line breaks and crazy spacing
notice that if i leave the star off the begining of the line,
the start is from the page edge, not the star line
public void moreOnJavadoc()
javadoc -d a_directory
javadoc -help
|
||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||