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

ID | Project | Category | View Status | Date Submitted | Last Update
0005412 | Part 06: TTCN-3 Control Interface | Clarification | public | 28-10-2009 16:15 | 18-03-2010 07:42

Reporter | tepelmann |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | major | Reproducibility | always
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.1.1 (published 2009-06) |
Target Version | v4.2.1 (published 2010-07) | Fixed in Version | v4.2.1 (published 2010-07) |
Clause Reference(s) | 9.2
Source (company - Author) |

Summary | 0005412: inconsistence in usage of types in TRI ANSI C value mapping

Description

In the ANSI C language mapping different issues regarding the usage of "long int" and "unsigned long int" could be observed.
1. In most of the tciSet/tciGet...Value(Value inst, ... position, ...) functions the parameter position is of type "unsigned long int". However in some "long int" is used, in some there is even a mix where for the set operation "unsigned long int" and for the get operation "long int" is used. As position should not be less then 0, "unsigned long int" should be appropriate here.
2. The same applies also for some tciGet/tciSet... functions.
3. TString[] is used where in the abstract data type type definition TStringSeq is defined. Also the mapping differs slightly. TString[] is mapped to "char**" where TStringSeq is mapped to "String*".

Steps To Reproduce |

Additional Information

Examples for 1. and 2.:
void tciSetCStringCharValue (Value inst, long int position, char value)
char tciGetCStringCharValue (Value inst, long int position)
int tciGetBStringBitValue (Value inst, long int position)
void tciSetBStringBitValue (Value inst, unsigned long int position, int value)
unsigned long int tciGetBStringLength(Value inst)
void tciSetBStringLength (Value inst, long int len)
long int tciGetHStringLength(Value inst)
void tciSetHStringLength (Value inst, unsigned long int len)

Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
28-10-2009 16:15 | tepelmann | New Issue |
28-10-2009 16:15 | tepelmann | Status | new => assigned
28-10-2009 16:15 | tepelmann | Assigned To | => Ina Schieferdecker
28-10-2009 16:15 | tepelmann | Clause Reference(s) | => 9.2
28-10-2009 16:15 | tepelmann | Source (company - Author) | =>
07-12-2009 13:57 | Ina Schieferdecker | Target Version | => Edition 4.2.1 (not yet published)
15-02-2010 04:10 | Ina Schieferdecker | Note Added: 0009206 |
18-03-2010 07:41 | Ina Schieferdecker | Status | assigned => resolved
18-03-2010 07:41 | Ina Schieferdecker | Resolution | open => fixed
18-03-2010 07:41 | Ina Schieferdecker | Fixed in Version | => Edition 4.2.1 (not yet published)
18-03-2010 07:42 | Ina Schieferdecker | Status | resolved => closed

Notes

(0009206)
Ina Schieferdecker
15-02-2010 04:10

There are no triSet/triGet functions - that inconcistency applies to TCI only. Also, String only (mapped to char *) is used in TRI only. The CR has been moved to TCI.