Legacy Issue Number: 13268
Source: Open Canarias, SL ( Adolfo Sanchez-Barbudo Herrera [X] (Inactive))
Problem's text: "the invocation of the operation returns a tuple"
discussion: it could be understood as an OCL Tuple, which doesn't apply.
suggestion: Replace "a tuple" by "an ordered tuple".
Reported: QVT 1.0 — Thu, 15 Jan 2009 05:00 GMT
Disposition: Resolved — QVT 1.1
The usage or OrderedTuple seems misguided since an ordinary OCL Tuple does very similar things
without a positional hazard and without noticeable lexical overhead.
Only the case of TupleLiteralEx/UnpackExp is plausibly defined in QVT 1.1 and neither of the QVT
implementations (SmartQVT or Eclipse QVT) support OrderedTuple.
Therefore eliminate TupleLiteralExp, UnpackExp and OrderedTupleType and
Note that there are no editing instructions for the grammar. It is not clear that OrderedTuples were
really supported at all.
Updated: Fri, 6 Mar 2015 20:58 GMT