ETSI's Bug Tracker - TTCN-3 Change Requests
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0008222 | TTCN-3 Change Requests | Clarification | public | 15-03-2024 08:34 | 22-11-2024 09:59

Reporter | Martin Hauch |
Assigned To | Tomas Urban |
Priority | normal | Severity | feature | Reproducibility | have not tried
Status | resolved | Resolution | open |
Platform |  | OS |  | OS Version |
Clause Reference(s) | TTCN-3 core language, chapter 8.2.3.1, EXAMPLE 4
For STF discussion |
Source (company - Author) | Devoteam GmbH, Martin Hauch

Summary | 0008222: Clarification for renaming module

Description

It is possible to import multiple times from one module. What is allowed for the renaming?
1. Always the same renamed-name
2. diffent names are allowed for each import-statement
import from VerylongModuleNameB -> ShortRule1 { type MytypeA} with {encode "Rule1"};
import from VerylongModuleNameB -> ShortRule2 { type MytypeB} with {encode "Rule2"};
If 'VerylongModuleNameB' should further not be used to avoid type-clash for the type, VerylongModuleNameB could also not used for the second import?
I.e.
import from VerylongModuleNameB -> ShortRule1 { type MytypeA} with {encode "Rule1"};
import from ShortRule1 -> ShortRule2 { type MytypeB} with {encode "Rule2"};
should be used, but this means that ShortRule1 is also not usable to identify a type. In case of the renaming semantic should the original module-name be usable to define a new module-definition, or should the name be usable for field- or enumeration-values in type definitions?
In my opinion the semantic of an alias-name would be easier to understand. This would allow multiple aliases for a module-name and the module-name itself is still valid to identify an object uniquely. The usage of the alias-names should be handled in the same manner as the module-name.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
15-03-2024 08:34 | Martin Hauch | New Issue |
19-11-2024 13:30 | Jens Grabowski | Note Added: 0016690 |
19-11-2024 13:31 | Jens Grabowski | Assigned To | => Jens Grabowski
19-11-2024 13:31 | Jens Grabowski | Status | new => assigned
22-11-2024 09:22 | Jens Grabowski | Assigned To | Jens Grabowski => Tomas Urban
22-11-2024 09:59 | Tomas Urban | Note Added: 0016704 |
22-11-2024 09:59 | Tomas Urban | Status | assigned => resolved

Notes

(0016690)
Jens Grabowski
19-11-2024 13:30

To be considered for implementation in major release.

(0016704)
Tomas Urban
22-11-2024 09:59

Moved to gitlab: https://labs.etsi.org/rep/mts/ttcn3/standard/-/issues/28 [^]