Community
Participate
Working Groups
Build 3.0M5 + JDTCore HEAD from 20031127 Following code in AND_ANDExpression: rightInfo.setReachMode(previousMode); // reset after trueMergedInfo got extracted gets formatted into: rightInfo.setReachMode(previousMode); // reset // after // trueMergedInfo // got // extracted
My settings were: - max code line length: 100 - max comment line length: 80
This is not done by our formatter. You have the formatting of comment selected. See Preferences>Java>Code formatter>Comments. If this is checked, then it should be moved to JDT/UI or change the preferences.
Move to JDT/UI.
What's your expectation?
I'd rather have the comment moved to next line if not a NON-NLS tag. One word per line is really unreadable...
*** Bug 49623 has been marked as a duplicate of this bug. ***
if the end of line comment was on a field decleration you could turn it into a /*...*/ comment before the field!
We could do this for all single-line comments that exceed the length. Having consecutive lines of single-line comments looks ugly.
*** Bug 47757 has been marked as a duplicate of this bug. ***
*** Bug 50899 has been marked as a duplicate of this bug. ***
*** Bug 50900 has been marked as a duplicate of this bug. ***
*** Bug 76543 has been marked as a duplicate of this bug. ***
*** Bug 76660 has been marked as a duplicate of this bug. ***
Ownership changed.
Using 3.3M5, line comment can be left untouched while formatting other comments is enabled (block and javadoc). I don't think the code formatter can do anything about the way the comment should be formatted. Moving it to the next line or the line before the statement can be misleading. Splitting it the way it is done right now is ugly. So I would simply recommend to disable line comment formatting. Any thought?
The new option to disable the line comment formatting should be used. No further action plan.