Constants with Java Compiler ?

Question

When recompiling java files which contains CONSTANTS, I mean static final variables,
I should also recompile the classes from
which these constants are referred to. Otherwise
I get buggy results. Is this an aimed result of
Java or a bug of Java, I wonder ?

Answer 1

my statement is TRUE also if the member is not declared as "final". When a Java Compiler do work,
it replaces "REFERENCES TO MEMBERS ASSIGNED CONSTANT VALUES" with their compile-time assigned values. Thus,
--------- here is A.java ----------
public class A {
public static void main(String [] str) {
System.out.println(""+ b.b);
---- here is B.java --------------
public class B {
static final int b = 10;
after producing A.class and B.class , if reproduce
B.class to have member b = 20 then,
java A
is gonna print out 10, so not displaying the real value ??
I think One class' compilation should not be dependent
to others classes' compilation. It seems to be a BUG of Java ? Does'nt ?
When recompiling java files which containsCONSTANTS,
I mean static final variables,
I should also recompile the classes from
which these constants are referred to. Otherwise
I get buggy results. Is this an aimed result of
Java or a bug of Java, I wonder ?static final int number = 3;
MyClass.number will be parsed to 3, since it's
guaranteed not to change unless you of course modify
the source.