This is true the type might not be always useful. I personnally benefit from it mainly because it reminds/helps me to describe type-specific constraints (i.e. preconditions), but this is true the drawback is that I spend less time providing a higher level description which would complete the intent provided by the parameter name.
For instance: @param counters a non-empty <code>Map</code> with String as keys and Integer as values However, I agree this may not be the common case and that if such content is proposed it should rather be in a template so that each programmer can fit its own needs. >* @param p1 a <code>Param1[]</code> value > I don't find this kind of generation (above) useful. The javadoc generator already knows the types from the parameters and publishes these in the resultant javadoc. I think the param fields should be initially blank as the automatic comments just provide redundant information, that which would already be in the docs and makes it harder to notice which javadocs haven't been completed. > >Paul. _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
