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

ID | Project | Category | View Status | Date Submitted | Last Update
0007599 | Part 01: TTCN-3 Core Language | Technical | public | 27-01-2017 08:56 | 30-12-2017 16:08

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.9.1 (published 2017-05) |
Target Version | v4.10.1 (published 2018-05) | Fixed in Version | v4.10.1 (published 2018-05) |
Clause Reference(s) | 5.4.2
Source (company - Author) | STF 521

Summary | 0007599: Rules for actual parameterers with template restriction

Description

The rules for template restrictions of actual in and out parameters in the restriction 5.4.2.d do not match those described in 15.8.b.
The first set of rules (5.4.2.d) say that templates with certain restriction cannot be used at all as an actual parameter while the second set of rules (15.8.b) states that only the content should be checked at the time of parameter assignment (dependent on the tool, in compile time or runtime).
Proposal:
Remove the hard restriction for in and out parameters from 5.4.2.d and replace it with a soft (content-related) restriction or a reference to the rules described in 15.8.

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

Relationships

related to | 0007603 | closed | Gyorgy Rethy | Delete note on template restriction passing table

Attached Files |

Issue History
Date Modified | Username | Field | Change
27-01-2017 08:56 | Tomas Urban | New Issue |
27-01-2017 10:49 | Jacob Wieland - Spirent | Note Added: 0014522 |
06-03-2017 12:21 | Tomas Urban | Relationship added | related to 0007603
17-04-2017 14:39 | szabados | Note Added: 0014562 |
06-06-2017 14:10 | Jens Grabowski | Note Added: 0014628 |
06-06-2017 14:11 | Jens Grabowski | Assigned To | => Tomas Urban
06-06-2017 14:11 | Jens Grabowski | Status | new => assigned
27-07-2017 11:31 | Tomas Urban | Note Added: 0014785 |
08-09-2017 07:45 | Tomas Urban | Note Added: 0014823 |
08-09-2017 07:45 | Tomas Urban | Status | assigned => resolved
08-09-2017 07:45 | Tomas Urban | Resolution | open => fixed
08-09-2017 07:45 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
30-12-2017 16:08 | Gyorgy Rethy | Status | resolved => closed
30-12-2017 16:08 | Gyorgy Rethy | Product Version | => v4.9.1 (published 2017-05)
30-12-2017 16:08 | Gyorgy Rethy | Fixed in Version | => v4.10.1 (published 2018-05)
30-12-2017 16:08 | Gyorgy Rethy | Target Version | => v4.10.1 (published 2018-05)

Notes

(0014522)
Jacob Wieland - Spirent
27-01-2017 10:49

The rules have been designed specifically to allow tools that do compile-time checking to help the user avoid unwanted situations and also allow tools to avoid runtime-checking.
Of course, this could also be changed into (then probably oftimes ignored) warnings and runtime-checks that only are done in case that a warning was issued, i.e. when the current hard conditions are violated.
From the user perspective, I still think that the hard restriction is more helpful as it helps identify potential problems better. These problems can be solved by adding/removing template restrictions to declarations and we often have found lots of real errors that way at compile-time which otherwise would have been very hidden and hard to trace back at runtime.

(0014562)
szabados
17-04-2017 14:39

Breaking the harder rules sounds very much like a badly constructed test architecture ... that might or might not run into an error. + these new cases will require some runtime overhead people might not be prepared for.

(0014628)
Jens Grabowski
06-06-2017 14:10

STF discussion: to be discussed during the week, Tomas to prepare discussion

(0014785)
Tomas Urban
27-07-2017 11:31

Resolution being prepared together with the resolution of 0007603.

(0014823)
Tomas Urban
08-09-2017 07:45

Resolved as a part of 0007603 (hard restriction will be used).