OrderOfElements
From APIDesign
(Difference between revisions)
(New page: Runtime BackwardCompatibility can be significantly influenced by changing the order of elements in a {{JDK|java/util|Collection}} or in an {{JDK|java/lang/reflect|Array}}. Sure, some p...) |
|||
| Line 1: | Line 1: | ||
| - | Runtime [[BackwardCompatibility]] can be significantly influenced by changing the order of elements in a {{JDK|java/util|Collection}} or in an {{JDK|java/lang/reflect|Array}}. Sure, some people would argue that depending on the order of items as served by {{JDK|java/util|HashSet}}.'''iterator()''' is unreasonable (and there is no doubt | + | Runtime [[BackwardCompatibility]] can be significantly influenced by changing the order of elements in a {{JDK|java/util|Collection}} or in an {{JDK|java/lang/reflect|Array}}. Sure, some people would argue that depending on the order of items as served by {{JDK|java/util|HashSet}}.'''iterator()''' is unreasonable (and there is no doubt about that), however there are less obvious cases. |
== [[JUnit]] and Switch to [[JDK]]7 == | == [[JUnit]] and Switch to [[JDK]]7 == | ||
Revision as of 09:30, 22 August 2011
Runtime BackwardCompatibility can be significantly influenced by changing the order of elements in a Collection or in an Array. Sure, some people would argue that depending on the order of items as served by HashSet.iterator() is unreasonable (and there is no doubt about that), however there are less obvious cases.
Follow
