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

ID | Project | Category | View Status | Date Submitted | Last Update
0007096 | Part 01: TTCN-3 Core Language | Clarification | public | 01-07-2015 12:21 | 14-12-2015 10:51

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
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) | 6.3.4
Source (company - Author) | Elvior

Summary | 0007096: Strong typing in redirect assignments

Description

The current rules (as specified in the section 6.3.4) require strong typing in the redirect assignment part of the receive or trigger operations.
However, redirect assignment can be used in the getcall, getreply and catch operation too, but it not explicitly mentioned in this section or any other section of the core language specification that strong typing is required in these case. This is not a very consistent solution. Compatibility rules shall be identical for all redirect assignments.
Proposed solution: The last sententence of the section 6.3.4 shall be modified so that it explicitly enumerates the above mentioned operations in the following way:
Strong typing also applies to storing the received value, parameters, address or component reference during a receive, trigger, getcall, getreply, catch or check operation.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7096_rules_overview.docx (15,404) 05-08-2015 14:32 http://oldforge.etsi.org/mantis/file_download.php?file_id=3235&type=bug CR7096_resolution_v1.docx (80,619) 21-09-2015 13:37 http://oldforge.etsi.org/mantis/file_download.php?file_id=3259&type=bug

Issue History
Date Modified | Username | Field | Change
01-07-2015 12:21 | Tomas Urban | New Issue |
01-07-2015 12:33 | Jacob Wieland - Spirent | Note Added: 0012993 |
01-07-2015 12:37 | Tomas Urban | Note Added: 0012994 |
03-08-2015 12:51 | Gyorgy Rethy | Note Added: 0013026 |
03-08-2015 12:51 | Gyorgy Rethy | Assigned To | => Axel Rennoch
03-08-2015 12:51 | Gyorgy Rethy | Status | new => assigned
05-08-2015 14:32 | Axel Rennoch | File Added: CR7096_rules_overview.docx |
05-08-2015 14:33 | Axel Rennoch | Note Added: 0013087 |
06-08-2015 14:49 | Gyorgy Rethy | Note Added: 0013118 |
21-09-2015 13:37 | Axel Rennoch | File Added: CR7096_resolution_v1.docx |
21-09-2015 13:39 | Axel Rennoch | Note Added: 0013203 |
21-09-2015 13:39 | Axel Rennoch | Assigned To | Axel Rennoch => Jacob Wieland - Spirent
21-09-2015 13:39 | Axel Rennoch | Status | assigned => acknowledged
22-09-2015 08:04 | Jacob Wieland - Spirent | Note Added: 0013229 |
22-09-2015 08:04 | Jacob Wieland - Spirent | Status | acknowledged => resolved
22-09-2015 08:04 | Jacob Wieland - Spirent | Fixed in Version | => v4.8.1 (published 2016-07)
22-09-2015 08:04 | Jacob Wieland - Spirent | Resolution | open => fixed
16-10-2015 13:29 | Jacob Wieland - Spirent | Status | resolved => feedback
16-10-2015 13:29 | Jacob Wieland - Spirent | Resolution | fixed => reopened
16-10-2015 13:30 | Jacob Wieland - Spirent | Status | feedback => resolved
16-10-2015 13:30 | Jacob Wieland - Spirent | Resolution | reopened => fixed
16-10-2015 13:30 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
04-11-2015 14:00 | Gyorgy Rethy | Target Version | => v4.8.1 (published 2016-07)
14-12-2015 10:51 | Gyorgy Rethy | Note Added: 0013608 |
14-12-2015 10:51 | Gyorgy Rethy | Status | resolved => closed

Notes

(0012993)
Jacob Wieland - Spirent
01-07-2015 12:33

I disagree, strong typing is necessary only for the matching-part because there the concrete type is used as type-hypothesis for the codec. For the redirection-assignment part it is not necessary as the result can also be stored in a compatible variable.
Lessening this restriction would be backward compatible, while imposing the same restriction on the other operations would be backward incompatible.

(0012994)
Tomas Urban
01-07-2015 12:37

I have no objections against Jacob's proposal. It removes inconsistent rules for handling redirect assignments and that was the main objective of this CR.

(0013026)
Gyorgy Rethy
03-08-2015 12:51

STF discussion 03-08-2015: as first step collect type compatibility rules for all kinds of redirect (value, address,...) and for all types of receiving operations.

(0013087)
Axel Rennoch
05-08-2015 14:33

various rules have been identified and collected in a table, see uploaded file

(0013118)
Gyorgy Rethy
06-08-2015 14:49

STF discussion 06-08-2015: The rules are currently not fully consistent, we shall make them harmonized throughout the standard. The STF doesn't see a technical reason to keep strong typing for the storing part of communication operations (for the message and from matching parts strong typing is required).
Before making the changes let leave time for comments. If no objection is received until the next STF session (w39, 21-25 September), prepare the text proposal.

(0013203)
Axel Rennoch
21-09-2015 13:39

Please have a look to the proposed changes in the uploaded resolution file.

(0013229)
Jacob Wieland - Spirent
22-09-2015 08:04

proposal ok

(0013608)
Gyorgy Rethy
14-12-2015 10:51

Added to draft V4.7.4