Issue 15711: UML 2.4 - ConditionalNode - Semantics (uml2-rtf)
Source: The MathWorks (Mr. Alan Moore, alan.moore(at)mathworks.co.uk)
Nature: Uncategorized Issue
Severity: 
Summary: The last paragraph of the semantics section of 12.3.18 ConditionalNode, states

 

Within the body section, variables defined in the loop node or in some higher-level enclosing node may be accessed and updated with new values. Values that are used in a data flow manner must be created or updated in all clauses of the conditional; otherwise, undefined values would be accessed.

 

I assume that the reference to ‘loop node’ is incorrect.

Resolution: 
Revised Text: 
Actions taken:
October 9, 2010: received issue
Discussion: 

End of Annotations:=====

m: Alan Moore <Alan.Moore@mathworks.co.uk>
To: "issues@omg.org" <issues@omg.org>
Date: Sat, 9 Oct 2010 10:39:51 +0100
Subject: UML 2.4 - ConditionalNode - Semantics
Thread-Topic: UML 2.4 - ConditionalNode - Semantics
Thread-Index: Actnlevrv/IzZWLyTd2Y0EzU1ir9Mw==
Accept-Language: en-US, en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB


The last paragraph of the semantics section of 12.3.18 ConditionalNode, states

 

Within the body section, variables defined in the loop node or in some higher-level enclosing node may be accessed and updated with new values. Values that are used in a data flow manner must be created or updated in all clauses of the conditional; otherwise, undefined values would be accessed.

 

I assume that the reference to .loop node. is incorrect.