Issue 11822: Giving an attribute a variable name and an expression value (marte-ftf) Source: Carleton University (Dr. Murray Woodside, cmw(at)sce.carleton.ca) Nature: Uncategorized Issue Severity: Summary: I am not clear of the status of this, but it seems that to use the profile flexibly one needs to be able to assign a variable name to an NFP, and also a value. Then the variable name can be used to change the value in studies, in a traceable way. The value can be an expression too. A possible resolution would be to allow expressions to read as variable = expression. Resolution: Resolution: This is already supported by VSL: A 'variable declaration' expression can have assigned an "initialExpression". Concretely, the following syntax has been adopted in VSL (page 402): <variable-declaration> ::= <variable-direction> '$' <variable-name> [<type-name>] ['=' <init-expression>] This means that you can have NFP values such as (extended notation): myLatency = (value= 5.0, expr= $var1=var2+var3/3, unit=ms) or the short notation: myLatency = (5.0, $var1=var2+var3/3, ms) Hence, this issue is close with no change. Revised Text: Disposition: Closed, no change Revised Text: Actions taken: December 19, 2007: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== te: Wed, 19 Dec 2007 16:57:44 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: issues@omg.org Subject: Giving an attribute a variable name and an expression value I am not clear of the status of this, but it seems that to use the profile flexibly one needs to be able to assign a variable name to an NFP, and also a value. Then the variable name can be used to change the value in studies, in a traceable way. The value can be an expression too. A possible resolution would be to allow expressions to read as variable = expression. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca Subject: Issue 11822: Giving an attribute a variable name and an expression value Date: Fri, 15 Feb 2008 17:30:32 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue 11822: Giving an attribute a variable name and an expression value thread-index: Achv8BVP3omxFg8+TPSVcQzAbDv0ug== From: "ESPINOZA Huascar 218344" To: X-OriginalArrivalTime: 15 Feb 2008 16:30:32.0711 (UTC) FILETIME=[15B58170:01C86FF0] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m1FGXpa1003019 Hi all, Issue 11822 (see below) with resolution: closed, no change, (with the agreement of the source: Murray) has been uploaded to the wiki. Cheers, Huascar -- Huascar ESPINOZA, Ph.D. CEA Saclay DRT/DTSI/SOL/LISE 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 France --- OMG Issue No: 11822 Title: Giving an attribute a variable name and an expression value Source: Carleton University (Dr. Murray Woodside, cmw@sce.carleton.ca) Summary: I am not clear of the status of this, but it seems that to use the profile flexibly one needs to be able to assign a variable name to an NFP, and also a value. Then the variable name can be used to change the value in studies, in a traceable way. The value can be an expression too. A possible resolution would be to allow expressions to read as variable = expression. Resolution: This is already supported by VSL: A 'variable declaration' expression can have assigned an "initialExpression". Concretely, the following syntax has been adopted in VSL (page 402): ::= '$' [] ['=' ] This means that you can have NFP values such as (extended notation): myLatency = (value= 5.0, expr= $var1=var2+var3/3, unit=ms) or the short notation: myLatency = (5.0, $var1=var2+var3/3, ms) Hence, this issue is close with no change. (http://www.sce.carleton.ca/faculty/woodside.html)