The Javadoc to win the details

This thought that the development of experienced colleagues proposed a modification has a problem, I hope to change, the old-timers speak, guilty of the tight, immediately looked at the next, the problem is that my method notes wrote a

** doesn‘t **

Suggested instead

doesnot

Said this generation Javadoc have a problem, gee, can't help but confused, this writing I remember not violate the grammar rules of Javadoc.
But the predecessor said must not be empty, quickly consult Oracle's Javadoc document
How to write the Docdocument for Javadoc tool and several other articles. I don't seem to have a problem with that.
Then use Android Studio to write the example generated Javadoc,still seems fine.
What ' s wrong~
Or to follow Yi decree changed it, after the later discussion, cough is a definite yin after all.
nn

By the way Javadoc, is really simple and practical tools, usually require themselves even write small works to follow Javadoc write comments, only need to know the basic grammar rules, you can comb and show others when used, is very worth recommending everyone to use,, the specific syntax is not in this said, After all, so easy. The main use of the core or meticulous, to these simple rules can be applied to things, the most important thing is meticulous, the details determine everything. Like a well-written algorithm that everyone quickly writes, the structure and naming rules of code can show both accomplishment and experience.
That ' s all~

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

The Javadoc to win the details