ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0005103 | Part 06: TTCN-3 Control Interface | Clarification | public | 21-04-2009 12:38 | 30-12-2010 17:11

Reporter | Stephan Schulz |
Assigned To | Ina Schieferdecker |
Priority | low | Severity | major | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v3.4.1 (published 2008-09) |
Target Version | v4.3.1 (published 2011-06) | Fixed in Version | v4.3.1 (published 2011-06) |
Clause Reference(s) | 7.2.2
Source (company - Author) | STF 370 - Stephan Schulz

Summary | 0005103: Handling of nested types/values unclear in TCI type and value interface
Description | For the given type definition: type record PEarlyMedia { FieldName fieldName(P_EARLY_MEDIA_E), record of charstring em_param } We wonder how it is possible to query the type of the second field or similarly how to instantiate values of the second field. Currently section 7.2.2 has no explcit hints how to deal with nested types/values.
Steps To Reproduce |
Additional Information | Core langaugae states for example: 6.2.1.3 Nested type definitions for field types TTCN-3 supports the definition of types for record fields nested within the record definition. Both the definition of new structured types (record, set, enumerated, set of, record of, and union) and the specification of subtype constraints are possible.
Tags | No tags attached.

Relationships

related to | 0005101 | closed | Axel Rennoch | SIP Library | Inline type definition in early media heaader causes problems with TCI

Attached Files |

Issue History
Date Modified | Username | Field | Change
21-04-2009 12:38 | Stephan Schulz | New Issue |
21-04-2009 12:38 | Stephan Schulz | Status | new => assigned
21-04-2009 12:38 | Stephan Schulz | Assigned To | => Ina Schieferdecker
21-04-2009 12:38 | Stephan Schulz | Clause Reference(s) | => 7.2.2
21-04-2009 12:38 | Stephan Schulz | Source (company - Author) | => STF 370 - Stephan Schulz
21-04-2009 12:41 | Stephan Schulz | Relationship added | related to 0005101
04-01-2010 14:11 | Ina Schieferdecker | Note Added: 0009158 |
04-01-2010 14:12 | Ina Schieferdecker | Target Version | => Edition 5.1.1 (not yet published)
23-03-2010 13:00 | Gyorgy Rethy | Priority | normal => low
01-09-2010 14:15 | Ina Schieferdecker | Note Added: 0009677 |
01-09-2010 14:15 | Ina Schieferdecker | Note Edited: 0009677 |
01-09-2010 14:15 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Gyorgy Rethy
02-09-2010 16:53 | Ina Schieferdecker | Note Added: 0009701 |
03-09-2010 10:25 | Gyorgy Rethy | Note Added: 0009706 |
03-09-2010 10:25 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Ina Schieferdecker
03-09-2010 10:25 | Gyorgy Rethy | Status | assigned => resolved
03-09-2010 10:25 | Gyorgy Rethy | Resolution | open => fixed
30-12-2010 17:11 | Ina Schieferdecker | Status | resolved => closed
30-12-2010 17:11 | Ina Schieferdecker | Fixed in Version | => Edition 4.3.1 (not yet published)

Notes

(0009158)
Ina Schieferdecker
04-01-2010 14:11

The TCI type interface defines: "TString getName() Returns the name of the type as defined in the TTCN 3 module." However, nested type definitions get implicit names only which are assigned by the TE. It needs to be discussed if there should be a standardized way to name/access nested type definitions or to make this a tool dependent feature. Postponed to 2010.

(0009677)
Ina Schieferdecker
01-09-2010 14:15

Proposal to resolve the CR as follows: ------------ TString getName() Returns the name of the type as defined in the TTCNâ€‘3 module. If the type is a nested type without explicit name, the TE has to create an additional unique identifier for this type which is consistently used in TRI/TCI. ------------ Please check.

(0009701)
Ina Schieferdecker
02-09-2010 16:53

Proposal to give an example rule for the naming of nested types following the part 1 approach:
----------------
TString getName()
Returns the name of the type as defined in the TTCNâ€‘3 module. If the type is a nested type without explicit name, the TE has to create an additional unique identifier for this type which is consistently used in TRI/TCI.
NOTE 1: The creation of identifiers for nested types is tool dependent.
NOTE 2: The naming for a nested type without explicit name can follow the rules defined in $6.2.1.1 and $6.2.3.2 of part 1, e.g. TypeIdOrExpression.ElementId and TypeId[-], respectively.
----------------

(0009706)
Gyorgy Rethy
03-09-2010 10:25

Reviewed, it's OK.