-
Key: OCL25-211
-
Status: open
-
Source: Model Driven Solutions ( Dr. Edward Willink)
-
Summary:
The pseudocode for OrderedSet::insertAt assumes that the inserted element is not already contained.
Presumably insertion of an existing element does not increase the OrderedSet size.
Design choice. Is the old element retained or is the old element removed and the new element inserted? The latter might preserve the postcondition that the element at the index is the inserted object, but what if the removed element was earlier so that everything moved along first?
Surely the only predictable behavior is that the old element is retained?
-
Reported: OCL 2.4 — Fri, 7 Jul 2017 08:29 GMT
-
Updated: Fri, 7 Jul 2017 09:38 GMT
OCL25 — OrderedSet::insertAt unclear for insert of existing element
- Key: OCL25-211
- OMG Task Force: Object Constraint Language 2.5 RTF