UML 2.6 RTF Avatar
  1. OMG Issue

UMLR — Why can’t the operand be a stringExpression

Open Closed All
  • Key: UMLR-573
  • Legacy Issue Number: 17863
  • Status: open  
  • Source: Model Driven Solutions ( Dr. Edward Willink)
  • Summary:

    Too many 'all's; remove all in front of all the component values.

    Suggest just: ... concatenating the ordered String values of each operand or subExpression.

    Simpler body: if subExpression->notEmpty()then subExpression->iterate(se; stringValue: String = '' | stringValue + se.stringValue())else operand->iterate(op; stringValue: String = '' | stringValue + op.stringValue())endifif notbody: subExpression->sum() + operand->sum()
  • Reported: UML 2.4.1 — Wed, 26 Sep 2012 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT