ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details
0000423Part 06: TTCN-3 Control InterfaceTechnicalpublic24-11-2006 14:4906-12-2007 11:11
Stephan Schulz 
Ina Schieferdecker 
highminorN/A
closedfixed 
v3.1.1 (published 2005-06) 
v3.3.1 (published 2008-04)v3.3.1 (published 2008-04) 
7.2.2.2.11
Siemens
0000423: Encode/Decode of empty record
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)
Proposed Solution:
There should be one more operation that initializes an empty record of a certain "type" of data.
No tags attached.
zip 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
24-11-2006 14:49Stephan SchulzNew Issue
24-11-2006 14:49Stephan SchulzClause Reference(s) => 7.2.2.2.11
24-11-2006 14:49Stephan SchulzSource (company - Author) => Siemens
24-11-2006 14:49Stephan SchulzNote Added: 0000323
24-11-2006 14:49Stephan SchulzStatusnew => feedback
24-11-2006 15:02Stephan SchulzNote Added: 0000328
15-06-2007 19:17Stephan SchulzStatusfeedback => assigned
15-06-2007 19:17Stephan SchulzAssigned To => Ina Schieferdecker
18-10-2007 13:10Ina SchieferdeckerTarget Version => Edition 3.3.1 (not yet published)
03-12-2007 15:40Thomas DeißNote Added: 0004243
04-12-2007 14:40Ina SchieferdeckerNote Added: 0004266
04-12-2007 14:40Ina SchieferdeckerFile Added: es_20187306v030301_CR423.zip
04-12-2007 14:41Ina SchieferdeckerNote Added: 0004267
04-12-2007 14:47Ina SchieferdeckerResolutionopen => fixed
04-12-2007 16:37Ina SchieferdeckerAssigned ToIna Schieferdecker => Thomas Deiß
04-12-2007 17:13Thomas DeißNote Added: 0004292
04-12-2007 17:13Thomas DeißStatusassigned => resolved
04-12-2007 17:14Thomas DeißStatusresolved => feedback
04-12-2007 17:14Thomas DeißResolutionfixed => reopened
04-12-2007 17:14Thomas DeißNote Added: 0004293
04-12-2007 17:15Thomas DeißAssigned ToThomas Deiß => Ina Schieferdecker
04-12-2007 17:15Thomas DeißStatusfeedback => resolved
04-12-2007 17:15Thomas DeißResolutionreopened => fixed
06-12-2007 11:11Ina SchieferdeckerStatusresolved => closed
06-12-2007 11:11Ina SchieferdeckerFixed 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