-
Key: QVT13-28
-
Legacy Issue Number: 19505
-
Status: closed
-
Source: Model Driven Solutions ( Dr. Edward Willink)
-
Summary:
The current phrasing
Within a contextual operation <it>result</it> represents the unique result parameter (if there is a unique declared result) or the
tuple containing the list of declared result parameters.suggests that the synthetic Tuple return is accessible as result. This is not necessary and imposes considerable implementation difficulties since a new Tuple would need creation with each mutation.
Sucggest the new wording.
Within a contextual operation for which no name is specified for a single return parameter, <it>result</it> is the implicit name of the parameter. If the name is specified explicitly, as is necessary for multiple returns, no pre-defined <it>result</it> variable exists.
-
Reported: QVT 1.2 — Wed, 2 Jul 2014 04:00 GMT
-
Disposition: Resolved — QVT 1.3
-
Disposition Summary:
Clarify availability of 'result' for Tuple returns
The current phrasing
Within a contextual operation result represents the unique result parameter (if there is a unique declared result) or the
tuple containing the list of declared result parameters.suggests that the synthetic Tuple return is accessible as result. This is not necessary and imposes considerable implementation difficulties since a new Tuple would need creation with each mutation.
Suggest the new wording.
Within a contextual operation for which no name is specified for a single return parameter, result is the implicit name of the parameter. If the name is specified explicitly, as is necessary for multiple returns, no pre-defined result variable exists.
Discussion
Yes
-
Updated: Tue, 29 Mar 2016 15:09 GMT