Issue 17863: Why can’t the operand be a stringExpression (uml25-ftf)
Source: Nomos Software (Dr. Edward Willink, ed(at)willink.me.uk)
Nature: Enhancement
Severity: Minor
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()

Resolution: 
Revised Text: 
Actions taken:
September 26, 2012: received issue
Discussion: 

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

Problem: 8.056

Severity: Minor
Type: enhancement
Location: 8.6 p 96 StringExpression Constraints
Title: Why can.t the operand be a stringExpression
Description:
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()
Source: Edward Willink