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

ID | Project | Category | View Status | Date Submitted | Last Update
0005918 | Part 01: TTCN-3 Core Language | Clarification | public | 25-07-2011 16:02 | 27-09-2011 11:38

Reporter | Uwe Truetsch |
Assigned To |  |
Priority | normal | Severity | minor | Reproducibility | always
Status | closed | Resolution | no change required |
Platform |  | OS |  | OS Version |
Product Version | v4.2.1 (published 2010-07) |
Target Version | v4.4.1 (published 2012-04) | Fixed in Version | v4.4.1 (published 2012-04) |
Clause Reference(s) | 6.2.1.3, 6.2.2.3
Source (company - Author) | NSN - Uwe Truetsch

Summary | 0005918: Accessing nested types within record and set types not explicitly stated in the spec

Description

Within clause 6.2.1.3 and 6.2.2.3 it is not specified that the user can access types of record fields.
It is not clear whether only those types shall be accessible which are defined within the record/set or whether it is generally possible for the types of all fields.
e.g.
type record R1 {
set { integer sf1, boolean sf2} f1,
boolean f2
}
const R1.f1 c1 := {1, true}; // is this ok?
const R1.f1.sf1 c1 := 2; // is this ok? It is actually not a nested type definition, it's a basic type instead
const R1.f2 c 3 := false; // is this ok?
Regardless what the original intention was I would opt for the general approach that all the types of the record/set fields shall be accessible.

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

Issue History
Date Modified | Username | Field | Change
25-07-2011 16:02 | Uwe Truetsch | New Issue |
25-07-2011 16:02 | Uwe Truetsch | Clause Reference(s) | => 6.2.1.3, 6.2.2.3
25-07-2011 16:02 | Uwe Truetsch | Source (company - Author) | => NSN - Uwe Truetsch
27-09-2011 11:38 | Gyorgy Rethy | Note Added: 0010241 |
27-09-2011 11:38 | Gyorgy Rethy | Status | new => closed
27-09-2011 11:38 | Gyorgy Rethy | Resolution | open => no change required
27-09-2011 11:38 | Gyorgy Rethy | Fixed in Version | => Edition 4.4.1
27-09-2011 11:38 | Gyorgy Rethy | Target Version | => Edition 4.4.1

Notes

(0010241)
Gyorgy Rethy
27-09-2011 11:38

It is explicitly written in the text, example 3 of $6.2.1.1 shows that all 3 cases are allowed.