You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we encounter a potential alias parameter like @author but have no alias entry, it would be nice if we could just interpret that line as a standard non-parameter line if possible.
The text was updated successfully, but these errors were encountered:
Hmpf. I am not sure that it is worth complicating and uglifying the otherwise beautiful design just for an invalid use case (@author makes a lot of sense for JavaDoc, but JavaDoc makes no sense with scripts).
I mean, yes, we can now go on and have a lengthy discussion about the merits and the downsides etc etc, but should we not perform some useful biological research instead?
If we go my route of a getCommentStyle and use EOL comment styles for that (e.g.: // for Java) then the "Javadoc" use case problem goes away.
We probably need to make that change anyway, to avoid other overly aggressive parsing situations. This problem will keep rearing its head in various forms until we fine tune things.
Reported in http://fiji.sc/bugzilla/show_bug.cgi?id=921
If we encounter a potential alias parameter like
@author
but have no alias entry, it would be nice if we could just interpret that line as a standard non-parameter line if possible.The text was updated successfully, but these errors were encountered: