Issue 6554: Clarify the UML semantics of IfExpEval (ocl2-rtf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: Author: Hubert Baumeister (baumeist@informatik.uni-muenchen.de),
Rolf Hennicker (hennicke@informatik.uni-muenchen.de),
Alexander Knapp (knapp@informatik.uni-muenchen.de)
Description: Clarify the UML semantics of IfExpEval
Rationale:
The specification on page 5-21 of the evaluation of if_then_else omits the case when the condition evaluates to undefined. Thus the sentence should read:
"The result value of an if expression is the result of the thenExpression if the condition is true, it is the result of the elseExpression if the condition is false, else it is undefined."

Resolution: The resolution for this becomes more complex with null/invalid rather than undefined. The resolution is in 17531.
Disposition: See issue 17531 for disposition
Revised Text: 
Actions taken:
November 11, 2003: received issue
December 23, 2013: closed issue
Discussion: 
Deferred for timing reasons
End of Annotations:=====
larify the UML semantics of IfExpEval
Author: Hubert Baumeister (baumeist@informatik.uni-muenchen.de),
Rolf Hennicker (hennicke@informatik.uni-muenchen.de),
Alexander Knapp (knapp@informatik.uni-muenchen.de)
Description: Clarify the UML semantics of IfExpEval
Rationale:
The specification on page 5-21 of the evaluation of if_then_else omits the case when the condition evaluates to undefined. Thus the sentence should read:
"The result value of an if expression is the result of the thenExpression if the condition is true, it is the result of the elseExpression if the condition is false, else it is undefined."