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

ID | Project | Category | View Status | Date Submitted | Last Update
0007115 | Part 01: TTCN-3 Core Language | Technical | public | 28-07-2015 13:45 | 11-12-2015 15:11

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) | 5.4.2
Source (company - Author) | STF 487

Summary | 0007115: Actual parameters of inout formal template parameters

Description

The following rule shall not include variables and formal value parameters:
Actual parameters that are passed to inout formal template parameters shall be variables, template variables, formal value or template parameters (of in, inout or out parameterization) of the current scope or references to elements of (template) variables or formal (template) parameters of structured types.
In its current form, the rule allows to pass a matching symbol to a non-template variable and therefore breaches one of the fundamental principles of TTCN-3. Consider this:
function f(inout template integer p) {
p := ?;
}
control {
var integer v;
f(v); // allowed, but the variable will contain ? after the call!!!
}
Proposal: Update the rule in the following way:
Actual parameters that are passed to inout formal template parameters shall be template variables, formal template parameters (of in, inout or out parameterization) of the current scope or references to elements of template variables or formal template parameters of structured types.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

related to | 0007114 | closed | Gyorgy Rethy | Actual parameters of out formal value parameters not defined

Attached Files |

Issue History
Date Modified | Username | Field | Change
28-07-2015 13:45 | Tomas Urban | New Issue |
28-07-2015 13:52 | Tomas Urban | Note Added: 0013007 |
03-08-2015 10:47 | Gyorgy Rethy | Note Added: 0013020 |
03-08-2015 10:47 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
03-08-2015 10:47 | Gyorgy Rethy | Status | new => assigned
25-09-2015 10:58 | Gyorgy Rethy | Target Version | => v4.8.1 (published 2016-07)
15-10-2015 12:51 | Jacob Wieland - Spirent | Relationship added | related to 0007114
15-10-2015 12:51 | Jacob Wieland - Spirent | Note Added: 0013404 |
15-10-2015 12:52 | Jacob Wieland - Spirent | Status | assigned => resolved
15-10-2015 12:52 | Jacob Wieland - Spirent | Resolution | open => fixed
04-11-2015 14:02 | Gyorgy Rethy | Fixed in Version | => v4.8.1 (published 2016-07)
11-12-2015 15:11 | Gyorgy Rethy | Note Added: 0013600 |
11-12-2015 15:11 | Gyorgy Rethy | Status | resolved => closed

Notes

(0013007)
Tomas Urban
28-07-2015 13:52

Please notice that the proposed solution was already a part of the accepted solution of CR6731, but for some reason it didn't get to the last version of the TTCN-3 core language specification.

(0013020)
Gyorgy Rethy
03-08-2015 10:47

STF discussion 03-08-2015: Culd be a potentially backward incompatible change. Ask tool vendors; send out a simple example code and ask for the result.

(0013404)
Jacob Wieland - Spirent
15-10-2015 12:51

resolved together with 7114

(0013600)
Gyorgy Rethy
11-12-2015 15:11

Resolved in CR 7114