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

ID | Project | Category | View Status | Date Submitted | Last Update
0007730 | Part 01: TTCN-3 Core Language | Editorial | public | 29-11-2017 12:30 | 04-01-2018 17:13

Reporter | KristÃ³f Szabados |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.9.1 (published 2017-05) |
Target Version | v4.10.1 (published 2018-05) | Fixed in Version | v4.10.1 (published 2018-05) |
Clause Reference(s) | A.1.5.0, A.1.6.6
Source (company - Author) | L.M. Ericsson

Summary | 0007730: "not_a_number" is not listed as a keyword but is used as such

Description

The special value "not_a_number" is not listed as keyword in table A.3
But at the same time the BNF defines it as a keyword:
"
421.NaNKeyword ::= "not_a_number"
"
And the text of the standard consistently treats it as a keyword.
For example:
"seed is infinity, -infinity or not_a_number. "
"The special values of the float type consist of infinity (positive infinity), -infinity (negative infinity) and the value not_a_number"
" typefloat Wrong (-infinity .. not_a_number);"

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
29-11-2017 12:30 | KristÃ³f Szabados | New Issue |
04-01-2018 17:08 | Gyorgy Rethy | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
04-01-2018 17:13 | Gyorgy Rethy | Note Added: 0014996 |
04-01-2018 17:13 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
04-01-2018 17:13 | Gyorgy Rethy | Status | new => closed
04-01-2018 17:13 | Gyorgy Rethy | Resolution | open => fixed
04-01-2018 17:13 | Gyorgy Rethy | Product Version | => v4.9.1 (published 2017-05)
04-01-2018 17:13 | Gyorgy Rethy | Fixed in Version | => v4.10.1 (published 2018-05)
04-01-2018 17:13 | Gyorgy Rethy | Target Version | => v4.10.1 (published 2018-05)

Notes

(0014996)
Gyorgy Rethy
04-01-2018 17:13

Implemented in V4.9.3. Problem existed, its resolution is trivial, resolved as proposed.