Community
Participate
Working Groups
------- Additional Comment #23 From Robert (Kraythe) Simmons 2005-06-28 05:10 [reply] ------- Reopening because "Mixed" mode tabs is still indenting improperly in RC3. The whole point of mixed mode indenting is to make sure that code indented with tabs appears the same on every machine no matter what the tab setting. Consider: public void classifySet(final Set<?> objects, final int value, final long other, final int device) { for (final Object element : objects) { System.out.println(element.getClass().getName()); } } Note that the second line of the argument list is lined up using spaces after the initial tab that lines it up with the numbers. There are no more tabs after the first one. I have my tab size set at 4 but this editor has a tab size of 8 and you can see if I paste in the "mixed" formatted text: public void classifySet(final Set<?> objects, final int value, final long other, final int device) { for (final Object element : objects) { System.out.println(element.getClass().getName()); } } It doesnt line up because of the varied tab size. However my first example will ALWAYS line up. The rule is simple. The phrase is inented to its block level with tabs but then spaces are used to line things up. ------- Additional Comment #24 From Thomas Singer 2005-06-28 05:20 [reply] ------- The whole point of tab-space mixture is to make the code looks well-aligned independently of the defined tab-size. There are some rules: - use tabs ONLY for leading indentation (convert all mid-line tabs to spaces) - when lines are wrapped, like in Robert's example, tabs must be used like for the first line of the wrapped statement, all further indentation must be spaces Robert's example with ---> as tabs and . as (leading) spaces to illustrate: --->public void classifySet(final Set<?> objects, final int value, final long other, --->........................final int device) { --->--->for (final Object element : objects) { --->--->--->System.out.println(element.getClass().getName()); --->--->} --->}
These got added to bug 49896
Should be marked as a duplicate of 49896 if this system has any remaining credibility.
Closing as invalid. It got entered by mistake, see details in bug 49896