Issue 19505: Clarify availability of 'result' for Tuiple returns (qvt-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Clarification Severity: Minor 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. Resolution: 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 Revised Text: In "8.1.16 Pre-defined Variables: this, self, and result" replace 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. by Within a contextual operation, result is the name of the unique result parameter, which is a tuple when there are multiple result parameters. When the name of a single result parameter is specified explicitly, no pre-defined result variable exists. Actions taken: July 2, 2014: received issue December 22, 2015: Resolved March 29, 2016: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 02 Jul 2014 12:04:46 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Edward Willink Employer: mailFrom: ed@willink.me.uk Terms_Agreement: Specification: QVT 1.2 Section: 8.1.16 FormalNumber: ptc/2014-03-38 Version: 1.2 Doc_Year: Year Doc_Month: Month Doc_Day: Day Page: 75 Title: Clarify availability of 'result' for Tuiple returns Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Remote Name: edwillink.plus.com Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.0; rv:30.0) Gecko/20100101 Firefox/30.0 Time: 12:04 PM Description: 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. Sucggest 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.