I found a code where it declared code like
private final static String API_RTN_SUCCESS = \"0\";
private final static String API_RTN_ERROR = \"1\";
public st
They are same,
private final static String API_RTN_ERROR = "1";
private static final String API_RTN_ERROR= "1";
it's the same, of course. it only depends on your habits and preference :-). I use public static final order for members and methods too
They are the same. The order of modifiers is not significant. And note that the same rule applies in all contexts where modifiers are used in Java.
However, most Java style guides recommend/mandate the same specific order for the modifiers. In this case, it is public static final
.
No difference at all. According to 8.3.1 - Classes - Field Modifiers of the Java Language Specification,
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.
For fields, the said production lists the modifiers in this order:
@Annotation
public
protected
private
static
final
transient
volatile
And for methods:
@Annotation
public
protected
private
abstract
static
final
synchronized
native
strictfp
private static final String API_RTN_ERROR= "1";
private final static String API_RTN_ERROR= "1";
static private final String API_RTN_ERROR= "1";
static final private String API_RTN_ERROR= "1";
final static private String API_RTN_ERROR= "1";
final private static String API_RTN_ERROR= "1";
even all above are same the position of first three is intercangeable.
This is just a convention or a practice people follow to keep coding style consistent. It improves the readability. so preferred way of writing this is
private static final <Type> <variable_name> = <value>;