| Issue 81: | Order the members of all classes by visibility | |
| Back to list |
To improve the readability of the source code, all variables, inner classes and methods of classes should be ordered by their name (ascending). Eclipse can do this automatically via "Source" > "Sort members".
It is possible to configure Eclipse to always sort members when saving a file ("Properties" > "Java Editor" > "Save actions" > "Configure" > "Code Organizing"). The sort order can be configured, unfortunately not in a per-project manner but only for the whole workspace ("Preferences" > "Java" > "Members Sort Order"). I highly recommend to sort members in the same category by visibility.
Mar 21, 2011
Project Member
#1
Skud...@googlemail.com
Status:
Fixed
Mar 21, 2011
This issue is not yet fixed. The existing source code has not been ordered yet.
Status:
Started
Mar 21, 2011
We do have to admit that there is [https://code.google.com/p/swp-dv-ws2010-osm-1/source/browse/trunk/TraceBook/src/tracebook/core/data/db/TagDbOpenHelper.java?r=698 one file] we have not ordered yet (because of some wonky forward declarations after reordering, gotta get some consultation), but all other source files have been reordered in r734, the commit before the closing one. Chances are you just have looked at r735 and decided that nothing else had been done before. For now, we can agree on not closing this issue until the very last file has been reordered.
Status:
Accepted
Owner: js.schrifterz@googlemail.com
Mar 22, 2011
WontFix because java does not allow using static fields before declaration.
Status:
WontFix
|