ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005413Part 06: TTCN-3 Control InterfaceClarificationpublic28-10-2009 16:3816-02-2010 06:59
Reportertepelmann 
Assigned ToIna Schieferdecker 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versionv4.1.1 (published 2009-06) 
Target Versionv4.2.1 (published 2010-07)Fixed in Versionv4.2.1 (published 2010-07) 
Clause Reference(s)9.5
Source (company - Author)     
Summary0005413: TciTypeClassType modified without setting explicit values
DescriptionObjid was removed from this part of the standard. Consequently also the TciTypeClassType was modified - TCI_OBJID_TYPE was removed.
However as no values were given to the enum entries all the entries following the former entry TCI_OBJID_TYPE will have a new value now.
If this was not intended, explicit values - like they exist in the Java mapping - should be applied. This can also be done for the IDL definition.
Steps To Reproduce
Additional InformationTCI_OBJID_TYPE had the implicit enum value 11, the following TCI_OCTETSTRING_TYPE the value 12. Without explicit value and removing the TCI_OBJID_TYPE, TCI_OCTETSTRING_TYPE will have the value 11.
TagsNo tags attached.
Relationships
parent of 0005475closed Ina Schieferdecker Some TCI constants without explicit values 
Attached Fileszip es_20187306v040102.zip (1,311,400) 15-02-2010 04:57
http://oldforge.etsi.org/mantis/file_download.php?file_id=2337&type=bug
Issue History
Date ModifiedUsernameFieldChange
28-10-2009 16:38tepelmannNew Issue
28-10-2009 16:38tepelmannStatusnew => assigned
28-10-2009 16:38tepelmannAssigned To => Ina Schieferdecker
28-10-2009 16:38tepelmannClause Reference(s) => 9.5
28-10-2009 16:38tepelmannSource (company - Author) =>
07-12-2009 13:56Ina SchieferdeckerTarget Version => Edition 4.2.1 (not yet published)
15-02-2010 04:55Ina SchieferdeckerNote Added: 0009208
15-02-2010 04:57Ina SchieferdeckerFile Added: es_20187306v040102.zip
15-02-2010 05:00Ina SchieferdeckerIssue cloned: 0005475
15-02-2010 05:00Ina SchieferdeckerRelationship addedparent of 0005475
15-02-2010 05:01Ina SchieferdeckerStatusassigned => resolved
15-02-2010 05:01Ina SchieferdeckerResolutionopen => fixed
15-02-2010 05:01Ina SchieferdeckerFixed in Version => Edition 4.2.1 (not yet published)
16-02-2010 06:59Ina SchieferdeckerStatusresolved => closed

Notes
(0009208)
Ina Schieferdecker   
15-02-2010 04:55   
There is also a gap between Boolean and Charstring and between Union and UniversalCharstring ... explicit values assigned as follows:

  TCI_ADDRESS_TYPE = 0,
  TCI_ANYTYPE_TYPE = 1,
  TCI_BITSTRING_TYPE = 2,
  TCI_BOOLEAN_TYPE = 3,
  TCI_CHARSTRING_TYPE = 5,
  TCI_COMPONENT_TYPE = 6,
  TCI_ENUMERATED_TYPE = 7,
  TCI_FLOAT_TYPE = 8,
  TCI_HEXSTRING_TYPE = 9,
  TCI_INTEGER_TYPE = 10,
  TCI_OCTETSTRING_TYPE = 12,
  TCI_RECORD_TYPE = 13,
  TCI_RECORD_OF_TYPE = 14,
  TCI_ARRAY_TYPE = 15,
  TCI_SET_TYPE = 16,
  TCI_SET_OF_TYPE = 17,
  TCI_UNION_TYPE = 18,
  TCI_UNIVERSAL_CHARSTRING_TYPE = 20,
  TCI_VERDICT_TYPE = 21

There has been also an inconcistency for the ARRAY type, which has been resolved in the Java mapping in favour of the IDL definition.

A clone CR created to discuss if to make the values for parameter passing mode, for component kind and for verdics also explicit in all mappings.