Logo etsi

ETSI's Bug Tracker
Main | My View | View Issues | Change Log | Roadmap | Monitor project
  
Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
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) 
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.
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.
Clause Reference(s)9.5
Source (company - Author)     
Attached Fileszip file icon es_20187306v040102.zip [^] (1,311,400 bytes) 15-02-2010 04:57

- Relationships
parent of 0005475closedIna Schieferdecker Some TCI constants without explicit values 

-  Notes
(0009208)
Ina Schieferdecker (reporter)
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.

- Issue History
Date Modified Username Field Change
28-10-2009 16:38 tepelmann New Issue
28-10-2009 16:38 tepelmann Status new => assigned
28-10-2009 16:38 tepelmann Assigned To => Ina Schieferdecker
28-10-2009 16:38 tepelmann Clause Reference(s) => 9.5
28-10-2009 16:38 tepelmann Source (company - Author) =>
07-12-2009 13:56 Ina Schieferdecker Target Version => Edition 4.2.1 (not yet published)
15-02-2010 04:55 Ina Schieferdecker Note Added: 0009208
15-02-2010 04:57 Ina Schieferdecker File Added: es_20187306v040102.zip
15-02-2010 05:00 Ina Schieferdecker Issue cloned: 0005475
15-02-2010 05:00 Ina Schieferdecker Relationship added parent of 0005475
15-02-2010 05:01 Ina Schieferdecker Status assigned => resolved
15-02-2010 05:01 Ina Schieferdecker Resolution open => fixed
15-02-2010 05:01 Ina Schieferdecker Fixed in Version => Edition 4.2.1 (not yet published)
16-02-2010 06:59 Ina Schieferdecker Status resolved => closed

MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker