Revisions to Immutablity in Java

removed ambiguous accentuation

Source Link

edited Nov 21, 2013 at 23:29

Sam

7.9k
1
26
51

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing (and thus, method overrides aswell)
... to methods prohibits method overrides
... to instance variables ensures immutabilityimmutability of these fields and thus also for whole objects, if specified for all, since final variables can just be written once, on construction.

Docs:

http://docs.oracle.com/javase/tutorial/essential/concurrency/immutable.html

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing (and thus, method overrides aswell)
... to methods prohibits method overrides
... to instance variables ensures immutability of these fields and thus also for whole objects, if specified for all, since final variables can just be written once, on construction.

Docs:

http://docs.oracle.com/javase/tutorial/essential/concurrency/immutable.html

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing (and thus, method overrides aswell)
... to methods prohibits method overrides
... to instance variables ensures immutability of these fields and thus also for whole objects, if specified for all, since final variables can just be written once, on construction.

Docs:

http://docs.oracle.com/javase/tutorial/essential/concurrency/immutable.html

deleted 8 characters in body

Source Link

edited Nov 21, 2013 at 22:50

Sam

7.9k
1
26
51

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing (and thus, method overrides aswell)
... to methods prohibits method overrides
... to instance variables ensures immutability of a instance variablesthese fields and thus also for whole objects, if specified for all.
Final, since final variables can just be written once, on construction.

Docs:

http://docs.oracle.com/javase/tutorial/essential/concurrency/immutable.html

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing (and thus, method overrides aswell)
... to methods prohibits method overrides
... to instance variables ensures immutability of a instance variables and thus also for whole objects, if specified for all.
Final variables can just be written once on construction.

Docs:

http://docs.oracle.com/javase/tutorial/essential/concurrency/immutable.html

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing (and thus, method overrides aswell)
... to methods prohibits method overrides
... to instance variables ensures immutability of these fields and thus also for whole objects, if specified for all, since final variables can just be written once, on construction.

Docs:

http://docs.oracle.com/javase/tutorial/essential/concurrency/immutable.html

deleted 28 characters in body

Source Link

edited Nov 21, 2013 at 22:42

Sam

7.9k
1
26
51

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing (and thus, method overrides aswell)
... to methods prohibits method overrides
... to instance variables ensures immutability of a instance variables and thus also for whole objects, if specified for all instance variables.
Final instance variables can just be written once on construction.

Docs:

http://docs.oracle.com/javase/tutorial/essential/concurrency/immutable.html

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing
... to methods prohibits method overrides
... to instance variables ensures immutability of a instance variables and thus also for whole objects, if specified for all instance variables.
Final instance variables can just be written once on construction.

Docs:

http://docs.oracle.com/javase/tutorial/essential/concurrency/immutable.html

There are substantial differences in the appliance of the final keyword.

Appliance...

... to classes prohibits sub-classing (and thus, method overrides aswell)
... to methods prohibits method overrides
... to instance variables ensures immutability of a instance variables and thus also for whole objects, if specified for all.
Final variables can just be written once on construction.

Docs: