Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Notes on Evolving APIs in Java 5"
| Line 1: | Line 1: | ||
| − | This page captures notes and discussions about API evolution guidelines in Java 5. The eventual output of these notes will be an update to the [[Evolving Java-based APIs]] document. | + | This page captures notes and discussions about API evolution guidelines in Java 5. The eventual output of these notes will be an update to the [[Evolving Java-based APIs]] document. General rule: the left-most bound of a generic type within API can never be changed. Bounds other than the left-most bound can be weakened without sacrificing compatibility. |
| + | == Generics == | ||
| + | |||
| + | Generics do not exist in the binary form of a class. Thus, binary compatibility of a class containing generics is reduced to compatibility of the [[http://java.sun.com/docs/books/jls/third_edition/html/typesValues.html#108979 erasure]] of the generic types. | ||
---- | ---- | ||
Back to [[API Central]] | Back to [[API Central]] | ||
Revision as of 18:25, 17 October 2006
This page captures notes and discussions about API evolution guidelines in Java 5. The eventual output of these notes will be an update to the Evolving Java-based APIs document. General rule: the left-most bound of a generic type within API can never be changed. Bounds other than the left-most bound can be weakened without sacrificing compatibility.
Generics
Generics do not exist in the binary form of a class. Thus, binary compatibility of a class containing generics is reduced to compatibility of the [erasure] of the generic types.
Back to API Central