ETSI's Bug Tracker - Part 01: TTCN-3 Core Language | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006424 | Part 01: TTCN-3 Core Language | Clarification | public | 19-02-2013 10:56 | 11-07-2013 10:28 |
| Reporter | Tomas Urban | ||||
| Assigned To | Ina Schieferdecker | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | v4.6.1 (published 2014-06) | Fixed in Version | v4.6.1 (published 2014-06) | ||
| Clause Reference(s) | C.4.1 | ||||
| Source (company - Author) | Elvior | ||||
| Summary | 0006424: Ambiguous rule in the regexp function | ||||
| Description | The regexp function specification contains the following rule: "The type of expression shall be universal charstring only when the type of inpar is universal charstring." It seems quite straightforward, but the specification contains compatibility rules for character strings too. These rules allow to use universal string values (if conditions are fulfilled) as character string values. The question if the above mentioned regexp rule overrides the compatility rule or not. Proposal: The current rule shall be amended: The type ... universal charstring. The compatibility rules for character string values specified in 6.3.1 cannot be applied in this case. (If compatibility rules cannot be used) or The type ... universal charstring or the expression can be interpreted as a character string according to the compatibility rules specified in 6.3.1. (If compatibility rules can be used) Alternative proposal: The regexp function signature can be changed so that the first two parameters and the return value are of the universal charstring type. This would still allow to use charstring values as parameters (as all charstrings can be interpreted as universal charstrings) and because the function result is always a substring of the first parameter, it can be safely used as a charstring value (using compatibility rules specified in 6.3.1). | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 19-02-2013 10:56 | Tomas Urban | New Issue | |||
| 19-02-2013 10:56 | Tomas Urban | Clause Reference(s) | => C.4.1 | ||
| 19-02-2013 10:56 | Tomas Urban | Source (company - Author) | => Elvior | ||
| 22-02-2013 11:23 | Jacob Wieland - Spirent | Note Added: 0011328 | |||
| 08-07-2013 15:37 | Jens Grabowski | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language | ||
| 08-07-2013 15:39 | Jens Grabowski | Status | new => assigned | ||
| 08-07-2013 15:39 | Jens Grabowski | Assigned To | => Jacob Wieland - Spirent | ||
| 08-07-2013 18:14 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2014-06) | ||
| 10-07-2013 11:54 | Gyorgy Rethy | Note Added: 0011497 | |||
| 10-07-2013 12:08 | Jacob Wieland - Spirent | Note Deleted: 0011328 | |||
| 10-07-2013 12:08 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Ina Schieferdecker | ||
| 11-07-2013 10:27 | Ina Schieferdecker | Status | assigned => resolved | ||
| 11-07-2013 10:27 | Ina Schieferdecker | Fixed in Version | => v4.6.1 (published 2014-06) | ||
| 11-07-2013 10:27 | Ina Schieferdecker | Resolution | open => fixed | ||
| 11-07-2013 10:28 | Ina Schieferdecker | Status | resolved => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||