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

ID | Project | Category | View Status | Date Submitted | Last Update
0003380 | Part 01: TTCN-3 Core Language | Clarification | public | 16-05-2008 09:44 | 12-12-2008 07:26

Reporter | Thomas DeiÃŸ |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version | v4.1.1 (published 2009-06) |
Clause Reference(s) | 6.1.2
Source (company - Author) | Nokia Siemens Networks, Thomas DeiÃŸ

Summary | 0003380: Renaming of component, port, address type

Description

From part1 it is unclear whether
type Type1 Type2;
would be valid if Type1 is a component or port types or if it is default, anytype, or address.
Clause 6.1.2 states
With user-defined types it is possible to create sub-types (such as lists, ranges and length restrictions) on basic types, structured types and anytype according to table 3.
Table 3 does not allow subtyping of component, port, default, and address.
I suggest to add a paragraph, that all types can be renamed. E.g.
6.1.2.6 Type Renaming
A type can be defined as a synonym to another type. This is applicable to all kinds of types.
type MyType1 MyType2;

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

Relationships

related to | 0004851 | closed | Ina Schieferdecker | Editorials on Part-1 v4.0.4

Attached Files | CR3380_TypeRenaming.doc (24,064) 17-08-2008 10:22 http://oldforge.etsi.org/mantis/file_download.php?file_id=1612&type=bug CR3380_TypeRenaming_02.doc (19,968) 18-08-2008 13:58 http://oldforge.etsi.org/mantis/file_download.php?file_id=1614&type=bug CR3380_TypeRenaming_03.doc (24,576) 12-12-2008 07:23 http://oldforge.etsi.org/mantis/file_download.php?file_id=1885&type=bug

Issue History
Date Modified | Username | Field | Change
16-05-2008 09:44 | Thomas DeiÃŸ | New Issue |
16-05-2008 09:44 | Thomas DeiÃŸ | Status | new => assigned
16-05-2008 09:44 | Thomas DeiÃŸ | Assigned To | => Ina Schieferdecker
16-05-2008 09:44 | Thomas DeiÃŸ | Clause Reference(s) | => 6.1.2
16-05-2008 09:44 | Thomas DeiÃŸ | Source (company - Author) | => Nokia Siemens Networks, Thomas DeiÃŸ
16-05-2008 09:44 | Thomas DeiÃŸ | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
17-08-2008 09:35 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
17-08-2008 10:22 | Ina Schieferdecker | File Added: CR3380_TypeRenaming.doc |
17-08-2008 10:23 | Ina Schieferdecker | Note Added: 0006546 |
17-08-2008 10:24 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Thomas DeiÃŸ
17-08-2008 10:24 | Ina Schieferdecker | Resolution | open => fixed
18-08-2008 13:58 | Thomas DeiÃŸ | File Added: CR3380_TypeRenaming_02.doc |
18-08-2008 14:01 | Thomas DeiÃŸ | Note Added: 0006560 |
18-08-2008 14:01 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Ina Schieferdecker
18-08-2008 14:01 | Thomas DeiÃŸ | Resolution | fixed => open
25-11-2008 15:11 | Ina Schieferdecker | Note Added: 0007416 |
25-11-2008 15:11 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Thomas DeiÃŸ
25-11-2008 15:11 | Ina Schieferdecker | Resolution | open => fixed
26-11-2008 08:08 | Thomas DeiÃŸ | Note Added: 0007434 |
26-11-2008 08:08 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Ina Schieferdecker
10-12-2008 12:28 | Ina Schieferdecker | Status | assigned => resolved
10-12-2008 12:28 | Ina Schieferdecker | Fixed in Version | => Edition 4.1.1 (not yet published)
12-12-2008 07:23 | Ina Schieferdecker | File Added: CR3380_TypeRenaming_03.doc |
12-12-2008 07:26 | Ina Schieferdecker | Status | resolved => closed
16-02-2009 05:26 | Ina Schieferdecker | Relationship added | related to 0004851

Notes

(0006546)
Ina Schieferdecker
17-08-2008 10:23

Resolution uploaded: proposal to make type renaming clause a subclause to clause 6 and not only to subclause to 6.1.2 as this applies to all and not only to basic types.

(0006560)
Thomas DeiÃŸ
18-08-2008 14:01

checked: I suggest to leave out the part on type compatibility. According to the usual type compatibility rules, synonym types are compatible. Except for enumerations. Note that
type enumeration A {a}
type enumeration B {a}
are _not_ compatible.
Alternatively: if type compatibility should be mentioned, let's add this as a note , mentioning also the case of enumerations.
I've uploaded a new resolution without mentioning type compatibility.

(0007416)
Ina Schieferdecker
25-11-2008 15:11

After discussion, synonym type should be compatible - this includes also enumerated types:
type enumerated E { a, b, c }
type E F;
var E e;
var F f;
e:= f; // is ok
To make this clear, clause 6.3.2.1 should be extended:
"Enumerated types are only compatible to synonym types (see clause 6.4) and never compatible with other basic or structured types (i.e. for enumerated types strong typing is required)."

(0007434)
Thomas DeiÃŸ
26-11-2008 08:08

ok.