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

ID | Project | Category | View Status | Date Submitted | Last Update
0000423 | Part 06: TTCN-3 Control Interface | Technical | public | 24-11-2006 14:49 | 06-12-2007 11:11

Reporter | Stephan Schulz |
Assigned To | Ina Schieferdecker |
Priority | high | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v3.1.1 (published 2005-06) |
Target Version | v3.3.1 (published 2008-04) | Fixed in Version | v3.3.1 (published 2008-04) |
Clause Reference(s) | 7.2.2.2.11
Source (company - Author) | Siemens

Summary | 0000423: Encode/Decode of empty record

Description

Currently there are three operations on RecordValue within TCI: getField, setField, and getFieldNames. There is however no operation that allows an empty record to be encoded/decoded. It should be also possible to encode/decode empty records. This extension is particularly helpful for quick-testing TTCN-3 code.
Empty records are not handled in TCI, but can be specified in TTCN-3. (part 6: 7.2.2.2.11, part 1: 6.3.1.0)

Steps To Reproduce |
Additional Information | Proposed Solution: There should be one more operation that initializes an empty record of a certain "type" of data.
Tags | No tags attached.
Relationships |
Attached Files | es_20187306v030301_CR423.zip (982,668) 04-12-2007 14:40 http://oldforge.etsi.org/mantis/file_download.php?file_id=1192&type=bug

Issue History
Date Modified | Username | Field | Change
24-11-2006 14:49 | Stephan Schulz | New Issue |
24-11-2006 14:49 | Stephan Schulz | Clause Reference(s) | => 7.2.2.2.11
24-11-2006 14:49 | Stephan Schulz | Source (company - Author) | => Siemens
24-11-2006 14:49 | Stephan Schulz | Note Added: 0000323 |
24-11-2006 14:49 | Stephan Schulz | Status | new => feedback
24-11-2006 15:02 | Stephan Schulz | Note Added: 0000328 |
15-06-2007 19:17 | Stephan Schulz | Status | feedback => assigned
15-06-2007 19:17 | Stephan Schulz | Assigned To | => Ina Schieferdecker
18-10-2007 13:10 | Ina Schieferdecker | Target Version | => Edition 3.3.1 (not yet published)
03-12-2007 15:40 | Thomas DeiÃŸ | Note Added: 0004243 |
04-12-2007 14:40 | Ina Schieferdecker | Note Added: 0004266 |
04-12-2007 14:40 | Ina Schieferdecker | File Added: es_20187306v030301_CR423.zip |
04-12-2007 14:41 | Ina Schieferdecker | Note Added: 0004267 |
04-12-2007 14:47 | Ina Schieferdecker | Resolution | open => fixed
04-12-2007 16:37 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Thomas DeiÃŸ
04-12-2007 17:13 | Thomas DeiÃŸ | Note Added: 0004292 |
04-12-2007 17:13 | Thomas DeiÃŸ | Status | assigned => resolved
04-12-2007 17:14 | Thomas DeiÃŸ | Status | resolved => feedback
04-12-2007 17:14 | Thomas DeiÃŸ | Resolution | fixed => reopened
04-12-2007 17:14 | Thomas DeiÃŸ | Note Added: 0004293 |
04-12-2007 17:15 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Ina Schieferdecker
04-12-2007 17:15 | Thomas DeiÃŸ | Status | feedback => resolved
04-12-2007 17:15 | Thomas DeiÃŸ | Resolution | reopened => fixed
06-12-2007 11:11 | Ina Schieferdecker | Status | resolved => closed
06-12-2007 11:11 | Ina Schieferdecker | Fixed in Version | => Edition 3.3.1 (not yet published)

Notes

(0000323)
Stephan Schulz
24-11-2006 14:49

Waiting for providers comments

(0000328)
Stephan Schulz
24-11-2006 15:02

Provider to clarify if CreateNewInstance solves the problem

(0004243)
Thomas DeiÃŸ
03-12-2007 15:40

If a record type does not contain any fields, then obviously it is not possible to set a field to a specific value, nor set a field to be absent or present.
But if a value of such a type is created, then it is uninitialized (see explanation of newInstance(), clause 7.2.2.1.).
This means there is no means to create an initialized value of an empty record type. Hence, none can be used for encoding/decoding.
I suggest to extend the TCI such that newly created instances of empty record and set types are considered initialized. Either a note could be added to the definition of newInstance() or to clause 7.2.2.11.
Creating 'empty' records of arbitrary record types is not considered a good solution as mandatory fields would still have to be uninitialized.

(0004266)
Ina Schieferdecker
04-12-2007 14:40

Notes to both the NewInstance description and section 7.2.2.11 added

(0004267)
Ina Schieferdecker
04-12-2007 14:41

The resolution is using already the updated text from CR2000 and CR2146.

(0004292)
Thomas DeiÃŸ
04-12-2007 17:13

checked by Thomas, ok.

(0004293)
Thomas DeiÃŸ
04-12-2007 17:14

dummy action to assign CR properly