Issue 13987: Minor typographical error in ImperativeIterateExp notation (qvt-rtf) Source: Open Canarias, SL (Mr. E. Victor Sanchez, vsanchez(at)opencanarias.com) Nature: Revision Severity: Minor Summary: Section 8.2.2.7, page 95: The text "list[condition]; // same as list->xselect(i; condition)" should read "list[condition]; // same as list->xselect(i | condition)". Notation of imperative iterate expressions state that the condition section must be separated from prior artifacts (iterators or target initializations), where present, by a "|" character, not a semicolon ";". Resolution: Duplicates in part Issue 13282. Disposition: See issue 13282 for disposition Revised Text: Actions taken: June 14, 2009: received issue July 15, 2014: closed issue Discussion: End of Annotations:===== te: Sun, 14 Jun 2009 10:52:50 +0100 Subject: Three Issues concerning the QVT specification From: Victor Sanchez To: Juergen Boldt Hello, Juergen! I want to submit three issues concerning the QVT specification. I know that Adolfo sends them to somebody who I think is you, so they get properly formatted in the issues page. If that is not the case, sorry for the e-mail and I would be grateful if you could point me to the right person for this task. Thank you very much! My name: E. Victor Sánchez Company name: Open Canarias, S.L. e-mail: vsanchez@opencanarias.com ********************************************** Nature: Revision Severity: Minor Title: Minor typographical error in ImperativeIterateExp notation Section 8.2.2.7, page 95: The text "list[condition]; // same as list->xselect(i; condition)" should read "list[condition]; // same as list->xselect(i | condition)". Notation of imperative iterate expressions state that the condition section must be separated from prior artifacts (iterators or target initializations), where present, by a "|" character, not a semicolon ";".