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

ID | Project | Category | View Status | Date Submitted | Last Update
0007459 | Part 01: TTCN-3 Core Language | Clarification | public | 22-07-2016 14:44 | 12-12-2016 10:10

Reporter | Jacob Wieland - Spirent |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.8.1 (published 2016-07) |
Target Version | v4.9.1 (published 2017-05) | Fixed in Version | v4.9.1 (published 2017-05) |
Clause Reference(s) | 27.1.2
Source (company - Author) | Spirent - Jacob Wieland

Summary | 0007459: the overwriting rules for attributes and the examples should be written more consistent

Description

There seems to be some confusion in the standard concerning the overwriting rules for attributes.
Especially the meaning of overriding the attribute in a lower scope is either not clear or it is not followed correctly in the EXAMPLE in 27.1.2.1 where MyType already has an encoding rule given by its surrounding module scope and no override is used to change that (though it is claimed to be changed by the parent encoding rule of the type MyPDUtwo in MyVariantsTwo.
The consensus in the STF is that the current intended (and probably implemented by most tools) meaning is this:
If a referenced type already has an encoding attached to it at the place of its definition (either by inheritance from its scope or direct annotation), that encoding 'wins' unless an encode attribute with override is inherited from the referencing definition's scope.
The text in the standard should be simplified/clarified in this regards and more (and correct) examples should be given to illustrate the different scenarios.
Still open questions are:
What is the meaning of encode/variant attributes on import statements?

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

Relationships

related to | 0007448 | closed | Gyorgy Rethy | Allowing multiple encodings for TTCN-3 types

Attached Files |

Issue History
Date Modified | Username | Field | Change
22-07-2016 14:44 | Jacob Wieland - Spirent | New Issue |
15-08-2016 11:26 | Jens Grabowski | Assigned To | => Tomas Urban
15-08-2016 11:26 | Jens Grabowski | Status | new => assigned
17-08-2016 11:24 | Jacob Wieland - Spirent | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
17-08-2016 11:24 | Jacob Wieland - Spirent | Product Version | => v4.8.1 (published 2016-07)
17-08-2016 11:24 | Jacob Wieland - Spirent | Target Version | => v4.9.1 (published 2017-05)
18-08-2016 09:49 | Tomas Urban | Relationship added | related to 0007448
18-08-2016 09:58 | Tomas Urban | Note Added: 0014151 |
18-08-2016 09:58 | Tomas Urban | Assigned To | Tomas Urban => Jacob Wieland - Spirent
18-08-2016 09:58 | Tomas Urban | Status | assigned => confirmed
18-08-2016 15:30 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => KristÃ³f Szabados
18-08-2016 15:30 | Jacob Wieland - Spirent | Status | confirmed => assigned
18-08-2016 15:30 | Jacob Wieland - Spirent | Status | assigned => confirmed
19-08-2016 13:35 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Jacob Wieland - Spirent
19-08-2016 13:35 | KristÃ³f Szabados | Status | confirmed => assigned
19-08-2016 15:00 | Jacob Wieland - Spirent | Note Added: 0014185 |
19-08-2016 15:00 | Jacob Wieland - Spirent | Status | assigned => confirmed
17-11-2016 10:00 | Jacob Wieland - Spirent | Note Added: 0014292 |
17-11-2016 10:00 | Jacob Wieland - Spirent | Status | confirmed => resolved
17-11-2016 10:00 | Jacob Wieland - Spirent | Fixed in Version | => v4.9.1 (published 2017-05)
17-11-2016 10:00 | Jacob Wieland - Spirent | Resolution | open => fixed
17-11-2016 10:00 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
12-12-2016 10:10 | Gyorgy Rethy | Note Added: 0014372 |
12-12-2016 10:10 | Gyorgy Rethy | Status | resolved => closed

Notes

(0014151)
Tomas Urban
18-08-2016 09:58

The issue has been addressed in 0007448 as a part of a complex change of attribute handling. Several modifications related to this CR have been made:
1. New rules for precedence of attributes (from strongest to lowest): direct use, inherited from a referenced type, inherited from a scope
2. New rule for import where import clause works as an additional scope unit lying between the importing and imported module. The attributes set this way are valid within the importing module only
3. Corrections in the mentioned example
Please check the proposed solution in the related CR.

(0014185)
Jacob Wieland - Spirent
19-08-2016 15:00

please review

(0014292)
Jacob Wieland - Spirent
17-11-2016 10:00

I have reviewed the text in the documents in the related CR and it was fine.

(0014372)
Gyorgy Rethy
12-12-2016 10:10

See CR 7448