Final (Java)

In the Java programming language, the codice_1 keyword is used in several contexts to define an entity that can only be assigned once.
Once a codice_1 variable has been assigned, it always contains the same value. If a codice_1 variable holds a reference to an object, then the state of the object may be changed by operations on the object, but the variable will always refer to the same object (this property of codice_1 is called "non-transitivity"). This applies also to arrays, because arrays are objects; if a codice_1 variable holds a reference to an array, then the components of the array may be changed by operations on the array, but the variable will always refer to the same array.
Final classes.
A final class cannot be subclassed. As doing this can confer security and efficiency benefits, many of the Java standard library classes are final, such as and .
Example:
public class ThisIsWrong extends MyFinalClass {...} // forbidden
Final methods.
A final method cannot be overridden or hidden by subclasses. This is used to prevent unexpected behavior from a subclass altering a method that may be crucial to the function or consistency of the class.
Example:
public class Base
public class Derived extends Base
 public void m1() {...} // OK, overriding Base#m1()
 public void m2() {...} // forbidden
 public static void m3() {...} // OK, hiding Base#m3()
 public static void m4() {...} // forbidden
A common misconception is that declaring a method as codice_1 improves efficiency by allowing the compiler to directly insert the method wherever it is called (see inline expansion). Because the method is loaded at runtime, compilers are unable to do this. Only the runtime environment and JIT compiler know exactly which classes have been loaded, and so only they are able to make decisions about when to inline, whether or not the method is final.
Machine code compilers that generate directly executable, platform-specific machine code, are an exception. When using static linking, the compiler can safely assume that methods and variables computable at compile-time may be inlined.
Final variables.
A final variable can only be initialized once, either via an initializer or an assignment statement. It does not need to be initialized at the point of declaration: this is called a "blank final" variable. A blank final instance variable of a class must be definitely assigned in every constructor of the class in which it is declared; similarly, a blank final static variable must be definitely assigned in a static initializer of the class in which it is declared; otherwise, a compile-time error occurs in both cases. (Note: If the variable is a reference, this means that the variable cannot be re-bound to reference another object. But the object that it references is still mutable, if it was originally mutable.)
Unlike the value of a constant, the value of a final variable is not necessarily known at compile time. It is considered good practice to represent final constants in all uppercase, using underscore to separate words.
Example:
public class Sphere {
 // pi is a universal constant, about as constant as anything can be.
 public static final double PI = 3.141592653589793;
 public final double radius;
 public final double xPos;
 public final double yPos;
 public final double zPos;
 Sphere(double x, double y, double z, double r) {
 radius = r;
 xPos = x;
 yPos = y;
 zPos = z;
Any attempt to reassign codice_7, codice_8, codice_9, or codice_10 will result in a compile error. In fact, even if the constructor doesn't set a final variable, attempting to set it outside the constructor will result in a compilation error.
To illustrate that finality doesn't guarantee immutability: suppose we replace the three position variables with a single one:
 public final Position pos;
where codice_11 is an object with three properties codice_12, codice_13 and codice_14. Then codice_11 cannot be assigned to, but the three properties can, unless they are final themselves.
Like full immutability, the use of final variables has great advantages, especially in optimization. For instance, codice_16 will probably have a function returning its volume; knowing that its radius is constant allows us to memoize the computed volume. If we have relatively few codice_16s and we need their volumes very often, the performance gain might be substantial. Making the radius of a codice_16 codice_1 informs developers and compilers that this sort of optimization is possible in all code that uses codice_16s.
Though it appears to violate the codice_1 principle, the following is a legal statement:
for (final SomeObject obj : someList) {
 // do something with obj
Since the obj variable goes out of scope with each iteration of the loop, it is actually redeclared each iteration, allowing the same token (i.e. codice_22) to be used to represent multiple variables.
Final variables in nested objects.
Final variables can be used to construct trees of immutable objects. Once constructed, these objects are guaranteed not to change anymore. To achieve this, an immutable class must only have final fields, and these final fields may only have immutable types themselves. Java's primitive types are immutable, as are strings and several other classes.
If the above construction is violated by having an object in the tree that is not immutable, the expectation does not hold that anything reachable via the final variable is constant. For example, the following code defines a coordinate system whose origin should always be at (0, 0). The origin is implemented using a codice_23 though, and this class defines its fields as public and modifiable. This means that even when reaching the codice_24 object over an access path with only final variables, that object can still be modified, as the below example code demonstrates.
import java.awt.Point;
public class FinalDemo {
 static class CoordinateSystem {
 private final Point origin = new Point(0, 0);
 public static void main(String[] args) {
 CoordinateSystem coordinateSystem = new CoordinateSystem();
 coordinateSystem.getOrigin().x = 15;
 assert coordinateSystem.getOrigin().getX() == 0;
The reason for this is that declaring a variable final only means that this variable will point to the same object at any time. The object that the variable points to is not influenced by that final variable though. In the above example, the origin's x and y coordinates can be freely modified.
To prevent this undesirable situation, a common requirement is that all fields of an immutable object must be final, and that the types of these fields must be immutable themselves. This disqualifies codice_25 and codice_23 and several other classes from being used in such immutable objects.
Final and inner classes.
When an anonymous inner class is defined within the body of a method, all variables declared codice_1 in the scope of that method are accessible from within the inner class. For scalar values, once it has been assigned, the value of the codice_1 variable cannot change. For object values, the reference cannot change. This allows the Java compiler to "capture" the value of the variable at run-time and store a copy as a field in the inner class. Once the outer method has terminated and its stack frame has been removed, the original variable is gone but the inner class's private copy persists in the class's own memory.
import javax.swing.*;
public class FooGUI {
 public static void main(String[] args) {
 //initialize GUI components
 final JFrame jf = new JFrame("Hello world!"); //allows jf to be accessed from inner class body
 jf.add(new JButton("Click me"));
 // pack and make visible on the Event-Dispatch Thread
 SwingUtilities.invokeLater(new Runnable() {
 @Override
 public void run() {
 jf.pack(); //this would be a compile-time error if jf were not final
 jf.setLocationRelativeTo(null);
 jf.setVisible(true);
 });
Blank final.
The blank final, which was introduced in Java 1.1, is a final variable whose declaration lacks an initializer. Previous to Java 1.1, a final variable was required to have an initializer. A blank final, by definition of "final", can only be assigned once. i.e. it must be unassigned when an assignment occurs. In order to do this, a Java compiler runs a flow analysis to ensure that, for every assignment to a blank final variable, the variable is definitely unassigned before the assignment; otherwise a compile-time error occurs.
final boolean hasTwoDigits;
if (number >= 10 && number < 100) {
 hasTwoDigits = true;
if (number > -100 && number <= -10) {
 hasTwoDigits = true; // compile-error because the final variable might already be assigned.
In addition, a blank final also has to be definitely assigned before being accessed. 
final boolean isEven;
if (number % 2 == 0) {
 isEven = true;
System.out.println(isEven); // compile-error because the variable was not assigned in the else-case.
Note though that a non-final local variable also needs to be definitely assigned before being accessed. 
boolean isEven; // *not* final
if (number % 2 == 0) {
 isEven = true;
System.out.println(isEven); // Same compile-error because the non-final variable was not assigned in the else-case.
C/C++ analog of final variables.
In C and C++, the analogous construct is the codice_29 keyword. This differs substantially from codice_1 in Java, most basically in being a type qualifier: codice_29 is part of the "type," not only part of the identifier (variable). This also means that the constancy of a value can be changed by casting (explicit type conversion), in this case known as "const casting". Nonetheless, casting away constness and then modifying the object results in undefined behavior if the object was originally declared codice_29. Java's codice_1 is a strict rule such that it is impossible to compile code that directly breaks or bypasses the final restrictions. Using reflection, however, it is often possible to still modify final variables. This feature is mostly made use of when deserializing objects with final members.
Further, because C and C++ expose pointers and references directly, there is a distinction between whether the pointer itself is constant, and whether the data pointed to by the pointer is constant. Applying codice_29 to a pointer itself, as in codice_35, means that the contents being referenced can be modified, but the reference itself cannot (without casting). This usage results in behaviour which mimics the behaviour of a codice_1 variable reference in Java. By contrast, when applying const to the referenced data only, as in codice_37, the contents cannot be modified (without casting), but the reference itself can. Both the reference and the contents being referenced can be declared as codice_29.
C# analogs for final keyword.
C# can be considered as similar to Java, in terms of its language features and basic syntax: Java has JVM, C# has .Net Framework; Java has bytecode, C# has MSIL; Java has no pointers (real memory) support, C# is the same. 
Regarding the final keyword, C# has two related keywords:
Note that a key difference between the C/C++ derived keyword codice_29 and the C# keyword codice_40 is that codice_29 is evaluated at compile time, while codice_40 is evaluated at runtime, and thus can has a expression that is only calculated and fixed later (at runtime).