Contents - Cultural View

Constant interface 101
}
public static final double PLANCK_CONSTANT = 6.62606896e-34;
This still leaves the original intent of the pattern mostly un-addressed (i.e. there is no syntax for accessing the
constants unqualified). However, since Java 5, consider using static import [2] to achieve the same goal:
import static Constants.PLANCK_CONSTANT;
import static Constants.PI;
public class Calculations {
}
public double getReducedPlanckConstant() {
}
return PLANCK_CONSTANT / (2 * PI);
To varying degrees, the issues listed above have now been addressed:
1. Because static members can be imported specifically, the class namespace need not be polluted with all members
of the constants interface.
2. Run-time and compile-time semantics are more closely aligned when using static imports instead of constants
interfaces.
3. The compiled code has one less binary compatibility constraint (that "class Calculations implements Constants").
4. Because static imports apply only to the current file (and not the whole class hierarchy) it is easier to discover
where each static member is declared.
5. There is less need to declare variables of the constants interface type, and it is potentially clearer that no concrete
instances actually exist.
Note however, the changes do nothing to improve the cohesion of the Constants class, so static imports should not be
considered to be a panacea.
References
[1] Bloch, Joshua, Effective Java, 2nd Edition, p. 98
[2] Sun Microsystems, Inc. (2004). "Static Import" (http:/ / java. sun. com/ j2se/ 1. 5. 0/ docs/ guide/ language/ static-import. html).