ETSI's Bug Tracker - Ext Pack: Extended TRI (ES 202 789)
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006330 | Ext Pack: Extended TRI (ES 202 789) | Editorial | public | 15-11-2012 12:08 | 13-12-2012 12:59

Reporter | Tomas Urban |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | text | Reproducibility | have not tried
Status | closed | Resolution | won't fix |
Platform |  | OS |  | OS Version |
Product Version | v1.1.1 (published 2012-04) |
Target Version | v1.2.1 (published 2013-04) | Fixed in Version |  |
Clause Reference(s) |
Source (company - Author) |

Summary | 0006330: Pointer value in C and C++ mapping

Description

The last item in the type_kind enumeration is called e_ptr (with void pointer as description).
There are two possible interpretation I could come up:
1. It indicates presence of a Value object. In this case the comment could be changed so that people dodn't get impression that any void pointer is suitable. I would prefer to change e_ptr to e_value or e_tci_value too, but that might be impossible for compatibility reasons. An alternative would be to add e_value/e_tci_value to the enumeration with the same value as e_ptr (as a synonym).
2. It indicates any content and it is up to the xtriConvert function to provide the conversion to a TCI value. In this case I would prefer to add e_value or e_tci_value to the enumeration to allow passing TCI values directly to the TE without need to execute the xtriConvert function.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

related to | 0006168 | closed | Ina Schieferdecker | xtriConvert should be located in xtriCommunicationSA instead of xtriCommunicationTE

Attached Files |

Issue History
Date Modified | Username | Field | Change
15-11-2012 12:08 | Tomas Urban | New Issue |
15-11-2012 12:25 | Tomas Urban | Summary | Value in C and C++ mapping => Pointer value in C and C++ mapping
15-11-2012 12:25 | Tomas Urban | Description Updated |
10-12-2012 13:50 | Gyorgy Rethy | Status | new => assigned
10-12-2012 13:50 | Gyorgy Rethy | Assigned To | => Ina Schieferdecker
10-12-2012 16:12 | Gyorgy Rethy | Target Version | => Edition 1.2.1 (ongoing)
13-12-2012 12:57 | Ina Schieferdecker | Relationship added | related to 0006168
13-12-2012 12:59 | Ina Schieferdecker | Note Added: 0011253 |
13-12-2012 12:59 | Ina Schieferdecker | Status | assigned => closed
13-12-2012 12:59 | Ina Schieferdecker | Resolution | open => won't fix

Notes

(0011253)
Ina Schieferdecker
13-12-2012 12:59

This issue was caused by the wrong placement of xtriConvert in extended TRI. Now that xtriConvert is placed in the right interface, it is not an issue anymore.