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

ID | Project | Category | View Status | Date Submitted | Last Update
0007501 | Part 06: TTCN-3 Control Interface | Technical | public | 27-09-2016 08:55 | 21-12-2016 13:49

Reporter | Tomas Urban |
Assigned To | Tomas Urban |
Priority | normal | Severity | major | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.9.1(ongoing) |
Target Version | v4.9.1(ongoing) | Fixed in Version | v4.9.1(ongoing) |
Clause Reference(s) | 8.3.3.1, 9.2, 10.5.3.2, 12.4.3.1
Source (company - Author) | Elvior

Summary | 0007501: Missing mapping of several methods of abstract TTCN-3 data types and values

Description

The methods getLowerTypeBoundary, getUpperTypeBoundary, getTypeLengthRestriction and getTypeMatchingMechanism defined in 7.2.2.1 are mapped only to C++, but not to other available languages (C, C++, C#). The same methods defined in 7.2.2.2.1 are mapped to java, C and C#, but not to C++. The newTemplate method is defined only for java, but not for C, C++ or C#.
Proposal: add missing mapping

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7505-1.docx (164,993) 18-11-2016 11:46 http://oldforge.etsi.org/mantis/file_download.php?file_id=3572&type=bug CR7505-2.docx (175,878) 02-12-2016 12:59 http://oldforge.etsi.org/mantis/file_download.php?file_id=3574&type=bug

Issue History
Date Modified | Username | Field | Change
27-09-2016 08:55 | Tomas Urban | New Issue |
14-11-2016 13:33 | Jens Grabowski | Assigned To | => Jacob Wieland - Spirent
14-11-2016 13:33 | Jens Grabowski | Status | new => assigned
18-11-2016 11:13 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Tomas Urban
18-11-2016 11:46 | Tomas Urban | File Added: CR7505-1.docx |
18-11-2016 11:49 | Tomas Urban | Note Added: 0014339 |
18-11-2016 11:49 | Tomas Urban | Assigned To | Tomas Urban => Jacob Wieland - Spirent
18-11-2016 11:49 | Tomas Urban | Status | assigned => confirmed
29-11-2016 12:15 | Jacob Wieland - Spirent | Note Added: 0014361 |
29-11-2016 12:15 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Tomas Urban
29-11-2016 12:15 | Jacob Wieland - Spirent | Status | confirmed => assigned
29-11-2016 13:49 | Tomas Urban | Assigned To | Tomas Urban => Jacob Wieland - Spirent
29-11-2016 13:49 | Tomas Urban | Note Added: 0014362 |
02-12-2016 12:59 | Tomas Urban | File Added: CR7505-2.docx |
02-12-2016 12:59 | Tomas Urban | Note Added: 0014363 |
02-12-2016 14:44 | Jacob Wieland - Spirent | Note Added: 0014364 |
02-12-2016 14:44 | Jacob Wieland - Spirent | Status | assigned => resolved
02-12-2016 14:44 | Jacob Wieland - Spirent | Fixed in Version | => v4.9.1(ongoing)
02-12-2016 14:44 | Jacob Wieland - Spirent | Resolution | open => fixed
02-12-2016 14:44 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Tomas Urban
21-12-2016 13:49 | Tomas Urban | Note Added: 0014473 |
21-12-2016 13:49 | Tomas Urban | Status | resolved => closed

Notes

(0014339)
Tomas Urban
18-11-2016 11:49

Proposal uploaded. Some C functions were added as a part of 0007505. Please review.

(0014361)
Jacob Wieland - Spirent
29-11-2016 12:15

why is the getTypeLengthRestriction, getTypeUpperBoundary, getTypeLowerBoundary and getTypeMatchingMechanism in the Value interface (and there with a different name)?

(0014362)
Tomas Urban
29-11-2016 13:49

That's because they are defined both for the Type and Value interface in the section 7. In my opinion, there should be just one definition on the Type level, but once we have both in the specification, it is simpler to provide mapping for both. Value function names are different, because C doesn't allow name overloading.

(0014363)
Tomas Urban
02-12-2016 12:59

The original proposal contained only C support. Java, C++ and C# were added to the second one. Please check.

(0014364)
Jacob Wieland - Spirent
02-12-2016 14:44

ok

(0014473)
Tomas Urban
21-12-2016 13:49

Added to draft 4.8.2