Description Jim des Rivieres 2002-11-06 15:46:26 EST

The class file editor uses a non-standard modifier order.  For instance,
    final public class java.lang.System extends java.lang.Object {
        final public static java.io.InputStream in;
        native private static void registerNatives();
        ...
It should instead read:
    public final class java.lang.System extends java.lang.Object {
        public static final java.io.InputStream in;
        private static native void registerNatives();
        ...

So says the Java Language Spec:
Section 8.1.1
http://java.sun.com/docs/books/jls/second_edition/html/classes.doc.html#21613

"ClassModifier: one of
	public protected private
	abstract static final strictfp

[...] If two or more class modifiers appear in a class declaration, then it is 
customary, though not required, that they appear in the order consistent with 
that shown above in the production for ClassModifier."

Section 8.3.1
http://java.sun.com/docs/books/jls/second_edition/html/classes.doc.html#78091

"FieldModifier: one of
	public protected private
	static final transient volatile

[...] If two or more (distinct) field modifiers appear in a field declaration, 
it is customary, though not required, that they appear in the order consistent 
with that shown above in the production for FieldModifier."

Section 8.4.3
http://java.sun.com/docs/books/jls/second_edition/html/classes.doc.html#78188

"MethodModifier: one of
	public protected private abstract static
	final synchronized native strictfp

[...] If two or more method modifiers appear in a method declaration, it is 
customary, though not required, that they appear in the order consistent with 
that shown above in the production for MethodModifier."