ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007124Part 01: TTCN-3 Core LanguageClarificationpublic05-08-2015 11:5213-10-2015 12:22
ReporterJacob Wieland - Spirent 
Assigned ToGyorgy Rethy 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versionv4.7.1 (published 2015-06) 
Target Versionv4.8.1 (published 2016-07)Fixed in Versionv4.8.1 (published 2016-07) 
Clause Reference(s)5.4.2
Source (company - Author)Testing Technologies - Jacob Wieland
Summary0007124: Semantics of Actual Parameter Assignment Notation ambiguous.
DescriptionAt the moment, the intended equivalency between an actual parameter list in assignment notation and an actual parameter list in list notation is not clearly stated in the standard.

The assignment notation is just supposed to be a syntactical shorthand notation
for a list notation where the assigned actual parameters are filled with the right-hand-side of the assignment and the actual parameters for all unassigned formal parameters are filled with their default values.

This will resolve tool-ambiguity between tools that already interpret assignment-notation in the way described above and those that evaluate assignment-notation in the textual order of assignments (instead of the order of definition in the formal parameter list.
Steps To Reproduce
Additional InformationThe semantic description of 5.4.2 should be sub-structured into several named paragraphs, e.g.

- Assignment-Notation
- Evaluation (including
-- evaluation order
-- lazy/fuzzy parameters
-- evaluation of out/inout parameters as left-hand-side expressions (with automatic left-hand-side-expansion)
-- passing back of out-parameters to actual parameters
)
- In, Out and Inout Parameters
- Default Parameters
- Special Parameters (Timers, Ports)

(not necessarily in that order)
TagsNo tags attached.
Relationships
related to 0007117closed Gyorgy Rethy The order of evaluation of actual and default parameters is not completely set 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
05-08-2015 11:52Jacob Wieland - SpirentNew Issue
05-08-2015 11:52Jacob Wieland - SpirentStatusnew => assigned
05-08-2015 11:52Jacob Wieland - SpirentAssigned To => Jens Grabowski
05-08-2015 12:03Jacob Wieland - SpirentRelationship addedrelated to 0007117
23-09-2015 13:32Jens GrabowskiNote Added: 0013268
23-09-2015 13:32Jens GrabowskiAssigned ToJens Grabowski => Jacob Wieland - Spirent
23-09-2015 15:11Jacob Wieland - SpirentNote Added: 0013273
23-09-2015 15:12Jacob Wieland - SpirentAssigned ToJacob Wieland - Spirent => Jens Grabowski
24-09-2015 16:23Jacob Wieland - SpirentNote Added: 0013297
24-09-2015 16:23Jacob Wieland - SpirentAssigned ToJens Grabowski => Gyorgy Rethy
24-09-2015 16:23Jacob Wieland - SpirentStatusassigned => confirmed
13-10-2015 12:20Gyorgy RethyProjectTTCN-3 Change Requests => Part 01: TTCN-3 Core Language
13-10-2015 12:20Gyorgy RethyProduct Version => v4.7.1 (published 2015-06)
13-10-2015 12:20Gyorgy RethyTarget Version => v4.8.1 (published 2016-07)
13-10-2015 12:22Gyorgy RethyNote Added: 0013366
13-10-2015 12:22Gyorgy RethyStatusconfirmed => closed
13-10-2015 12:22Gyorgy RethyResolutionopen => fixed
13-10-2015 12:22Gyorgy RethyFixed in Version => v4.8.1 (published 2016-07)

Notes
(0013268)
Jens Grabowski   
23-09-2015 13:32   
Jacob: Is this resolved with the resolution of CR 7117?

I don't see the need of restructuring 5.4.2. Your proposal for the restructuring seems also to include parts which go beyond pure restructuring?
(0013273)
Jacob Wieland - Spirent   
23-09-2015 15:11   
no, (see my last Note there). Basically, the original text should be changed to mention textual order of appearance and then adding the missing parameters with defaults at the end.
(0013297)
Jacob Wieland - Spirent   
24-09-2015 16:23   
resolved in 7117
(0013366)
Gyorgy Rethy   
13-10-2015 12:22   
Resolved by CR7117