Issue 13274: Page 84: Notation Section 8.2.1.22 MappingCallExp (qvt-rtf)
Source: Open Canarias, SL (Mr. Adolfo Sanchez-Barbudo Herrera, nobody)
Nature: Revision
Severity: Minor
Summary: Problem's text: ->forEach (cl) cleaningTransf.map removeDups(cl);
discussion: EBNF and forExp suggest using always braces to enclose the forExp body.
Suggestion: Enclose the forEach's body with '{' and '}'. Note that there are two forExps in this section
Resolution: yes
Revised Text: In 8.2.1.21 MappingCallExp replace
// first pass: cleaning the UML classes
uml->objectsOfType(Class) // invoking the imported transformation
->forEach (cl) cleaningTransf.map removeDups(cl);
// second pass: transforming all UML classes uml
->objectsOfType(Class)->forEach (cl)
cl.map umlclass2javaclass (); // equivalent to: this.map
umlclass2javaclass(cl)
by
// first pass: cleaning the UML classes
uml->objectsOfType(Class) // invoking the imported transformation
->forEach (cl) {
cleaningTransf.map removeDups(cl);
}
// second pass: transforming all UML classes uml
->objectsOfType(Class)->forEach (cl) {
cl.map umlclass2javaclass();
}// equivalent to: this.map umlclass2javaclass(cl)
Actions taken:
January 15, 2009: received issue
July 15, 2014: closed issue
Discussion: 

End of Annotations:=====
s is issue # 13274

Page 84: Notation Section 8.2.1.22 MappingCallExp

Problem's text: ->forEach (cl) cleaningTransf.map removeDups(cl);
discussion: EBNF and forExp suggest using always braces to enclose the forExp body.
Suggestion: Enclose the forEach's body with '{' and '}'. Note that there are two forExps in this section