ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006588 | Part 01: TTCN-3 Core Language | Clarification | public | 11-07-2013 18:02 | 27-08-2013 17:07

Reporter | Gyorgy Rethy |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | always
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.5.1 (published 2013-04) |
Target Version | v4.6.1 (published 2014-06) | Fixed in Version | v4.6.1 (published 2014-06) |
Clause Reference(s) | 6.3.1
Source (company - Author) | L.M.Ericsson

Summary | 0006588: Text string compatibility rules are ambiguous

Description

The first paragraph of 6.3.1 says: "For variables, constants, templates, etc. of simple basic types and basic string types the value "b" is compatible to type "A" if type "B" resolves to the same root type as type "A" (e.g. integer) and it does not violate subtyping (e.g. ranges, length restrictions) of type "A"."
Then, the last two paragraphs define compatibility rules between charstrings and universal charstrings, and allows implicit casting, i.e. the root types need not be the same.
Obviously, the first paragraph is meant for binary strings only, not for all string types.

Steps To Reproduce |
Additional Information | See proposed solution in the attached file.
Tags | No tags attached.
Relationships |
Attached Files | Char-Uchar_compatibility_resolution_v1.doc (68,096) 11-07-2013 18:02 http://oldforge.etsi.org/mantis/file_download.php?file_id=2841&type=bug Char-Uchar_compatibility_resolution_v2.doc (69,632) 27-08-2013 17:00 http://oldforge.etsi.org/mantis/file_download.php?file_id=2861&type=bug

Issue History
Date Modified | Username | Field | Change
11-07-2013 18:02 | Gyorgy Rethy | New Issue |
11-07-2013 18:02 | Gyorgy Rethy | File Added: Char-Uchar_compatibility_resolution_v1.doc |
11-07-2013 18:02 | Gyorgy Rethy | Clause Reference(s) | => 6.3.1
11-07-2013 18:02 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
11-07-2013 18:04 | Gyorgy Rethy | Assigned To | => Ina Schieferdecker
11-07-2013 18:04 | Gyorgy Rethy | Status | new => assigned
11-07-2013 18:04 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2014-06)
11-07-2013 18:05 | Gyorgy Rethy | Description Updated |
12-07-2013 09:06 | Jacob Wieland - Spirent | Note Added: 0011567 |
27-08-2013 17:00 | Ina Schieferdecker | File Added: Char-Uchar_compatibility_resolution_v2.doc |
27-08-2013 17:01 | Ina Schieferdecker | Note Added: 0011610 |
27-08-2013 17:06 | Ina Schieferdecker | Note Added: 0011611 |
27-08-2013 17:06 | Ina Schieferdecker | Status | assigned => resolved
27-08-2013 17:06 | Ina Schieferdecker | Resolution | open => fixed
27-08-2013 17:06 | Ina Schieferdecker | Fixed in Version | => v4.6.1 (published 2014-06)
27-08-2013 17:07 | Ina Schieferdecker | Status | resolved => closed

Notes

(0011567)
Jacob Wieland - Spirent
12-07-2013 09:06

I think it is not inconsistent. The general sentence states one condition when types are compatible. The additonal sentence weakens this condition for the special case. If the general sentence would contain an "only" or "if and only if" instead of simply "if", then it would really be inconsistent.

(0011610)
Ina Schieferdecker
27-08-2013 17:01

STF discussion: revert to original text and make the additional rules for charstring and universal charstring more explicit - see v2

(0011611)
Ina Schieferdecker
27-08-2013 17:06

As discussed.