Mike Aizatsky wrote: >So, the question is: are JavaDoc errors serious ones? The answer seems >to be "yes". If you have documentation, you must keep it consistent or >throw away. > >Do you agree? > In general I do, but in case you are trying to clean up a lot of old code with old, incorrect javadoc comments, you might want to do some code refactoring and cleanup first, and postpone fixing the javadoc problems until later. You might *have* to do it this way because there is some pressure to get a working system quickly, for example (regardless of whether this is good or bad programming practice or whether it leads to more work in the long run). In those cases I would like to have a way of showing javadoc errors in another color, or not analyzing them at all, in order to be able to concentrate on the actual code.
The way it works now, the Javadoc errors are partly destroying one of the main reasons why I use IDEA -- the fact that I can quickly see most of the syntactic and semantic errors in my code without having to actually compile everything. _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
