-
Key: OCL25-84
-
Legacy Issue Number: 15920
-
Status: open
-
Source: Model Driven Solutions ( Dr. Edward Willink)
-
Summary:
8.2 Does the lack of restriction on feature types for a TupleType extend to InvalidType and VoidType? With an InvalidType feature the tuple could only be 'well-formed' when containing an invalid value. Surely a tuple with an invalid value is itself invalid and not well-formed?
8.2.2 TupleType has some ASCII code corruptions in the OCL.
8.2.2 TupleType uses unqualified names for feature types allowing an ambiguity when package path is significant.
10.2 TupleValue surely values must not be invalid?
13 TupleLiteralExp has a TupleLiteralPart which has a Property, not accommodating the OclExpression of an initExpression provided by the concrete syntax. Surely a TupleLiteralPart is a derived VariableDeclaration adding an initExpression?
-
Reported: OCL 2.1 — Sat, 8 Jan 2011 05:00 GMT
-
Updated: Thu, 8 Oct 2015 14:12 GMT
OCL25 — OCL 2.3.TupleType semantics and AST
- Key: OCL25-84
- OMG Task Force: Object Constraint Language 2.5 RTF