February 2013
Intermediate to advanced
672 pages
16h 2m
English
This section describes the effects of changes to the declaration of a class and its members and constructors on pre-existing binaries.
If a class that was not declared abstract is changed to be declared abstract, then pre-existing binaries that attempt to create new instances of that class will throw either an InstantiationError at link time, or (if a reflective method is used) an InstantiationException at run time; such a change is therefore not recommended for widely distributed classes.
Changing a class that is declared abstract to no longer be declared abstract does not break compatibility with pre-existing binaries.
If a class that was not declared final is changed ...
Read now
Unlock full access