ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0007168 | Part 01: TTCN-3 Core Language | Editorial | public | 07-09-2015 13:26 | 09-12-2015 16:39

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | duplicate |
Platform |  | OS |  | OS Version |
Product Version | v4.7.1 (published 2015-06) |
Target Version | v4.8.1 (published 2016-07) | Fixed in Version | v4.8.1 (published 2016-07) |
Clause Reference(s) | 22.2.2
Source (company - Author) | STF 487

Summary | 0007168: Invalid description of redirect assignment of message fields in receive operation

Description

The section 22.2.2 states that: "In a single assignment within the list, on the left hand side of the assignment symbol (":=") a field of the template type shall be referenced, on the right hand side the name of the variable or a formal parameter, in which the value shall be stored."
However, this is clearly wrong. The (source) template field shall be on the right and the (target) variable on the left hand side of the assignment symbol. Both syntactical description and examples use that order. Besides, it is the common way how to write assignments. It would be very weird if redirect assignments behaved differently.
Proposal: Change the rule to:
In a single assignment within the list, on the right hand side of the assignment symbol (":=") a field of the template type shall be referenced, on the left hand side the name of the variable or a formal parameter, in which the value shall be stored.

Steps To Reproduce |
Additional Information |
Tags | technically agreed

Relationships

duplicate of | 0007090 | closed | Gyorgy Rethy | description and example for field value redirect are wrong

Attached Files |

Issue History
Date Modified | Username | Field | Change
07-09-2015 13:26 | Tomas Urban | New Issue |
07-09-2015 13:35 | Tomas Urban | Note Added: 0013192 |
07-09-2015 18:06 | Jacob Wieland - Spirent | Note Added: 0013194 |
07-09-2015 18:06 | Jacob Wieland - Spirent | Relationship added | duplicate of 0007090
21-09-2015 10:24 | Gyorgy Rethy | Target Version | => v4.8.1 (published 2016-07)
22-09-2015 09:40 | Gyorgy Rethy | Tag Attached: technically agreed |
22-09-2015 09:41 | Gyorgy Rethy | Note Added: 0013233 |
22-09-2015 09:41 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
22-09-2015 09:41 | Gyorgy Rethy | Status | new => assigned
15-10-2015 13:15 | Jacob Wieland - Spirent | Status | assigned => resolved
15-10-2015 13:15 | Jacob Wieland - Spirent | Resolution | open => duplicate
04-11-2015 14:03 | Gyorgy Rethy | Fixed in Version | => v4.8.1 (published 2016-07)
09-12-2015 16:39 | Gyorgy Rethy | Note Added: 0013576 |
09-12-2015 16:39 | Gyorgy Rethy | Status | resolved => closed

Notes

(0013192)
Tomas Urban
07-09-2015 13:35

The following rule shall be also changed to: "The variable or formal parameter shall be type compatible with the type of the field on the right hand side of the assignment symbol."

(0013194)
Jacob Wieland - Spirent
07-09-2015 18:06

already solved in CR 7090

(0013233)
Gyorgy Rethy
22-09-2015 09:41

STF discussion: comment is correct, may be solved by CR 7090 already. Check it and correct if still needed.

(0013576)
Gyorgy Rethy
09-12-2015 16:39

Added to draft V4.7.4