ETSI's Bug Tracker - Part 01: TTCN-3 Core Language |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006811 | Part 01: TTCN-3 Core Language | Technical | public | 05-11-2014 14:57 | 04-01-2015 20:11 |
|
| Reporter | Tomas Urban | |
| Assigned To | Gyorgy Rethy | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | v4.6.1 (published 2014-06) | |
| Target Version | v4.7.1 (published 2015-06) | Fixed in Version | v4.7.1 (published 2015-06) | |
| Clause Reference(s) | A.1.6.1.1 |
| Source (company - Author) | STF 478 |
|
| Summary | 0006811: Missing BNF support for lower bound exclustion in length restriction |
| Description | The BNF rule for the length restriction doesn't allow to use exclamation mark when defining the lower bound. The rule shall be changed from
44.StringLength ::= LengthKeyword "(" SingleExpression [".." Bound] ")"
to
44.StringLength ::= LengthKeyword "(" ["!"] SingleExpression [".." Bound] ")" |
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 05-11-2014 14:57 | Tomas Urban | New Issue | |
| 05-11-2014 14:57 | Tomas Urban | Status | new => assigned |
| 05-11-2014 14:57 | Tomas Urban | Assigned To | => Gyorgy Rethy |
| 06-11-2014 08:26 | Gyorgy Rethy | Note Added: 0012442 | |
| 06-11-2014 08:27 | Gyorgy Rethy | Note Added: 0012443 | |
| 06-11-2014 08:27 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Tomas Urban |
| 06-11-2014 08:27 | Gyorgy Rethy | Status | assigned => confirmed |
| 06-11-2014 08:58 | Tomas Urban | Note Added: 0012445 | |
| 06-11-2014 08:58 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy |
| 06-11-2014 12:34 | Gyorgy Rethy | Note Added: 0012459 | |
| 06-11-2014 12:35 | Gyorgy Rethy | Note Added: 0012460 | |
| 06-11-2014 12:35 | Gyorgy Rethy | Status | confirmed => resolved |
| 06-11-2014 12:35 | Gyorgy Rethy | Fixed in Version | => v4.7.1 (published 2015-06) |
| 06-11-2014 12:35 | Gyorgy Rethy | Resolution | open => fixed |
| 04-01-2015 20:11 | Gyorgy Rethy | Note Added: 0012610 | |
| 04-01-2015 20:11 | Gyorgy Rethy | Status | resolved => closed |
|
Notes |
|
|
|
Optional ! is added to Bound due to special values in range constraints, where they have well defined semantics (because special values have concrete encodings)
In case of length adding ! would complicate the language without obvious advantage and it would be difficult -if not impossible - to explain the semantics of ..!infinity.
Let's go the opposite way and add the static semantics rule excluding ! for length contraints:
44.StringLength ::= LengthKeyword "(" SingleExpression [".." Bound] ")"
/* STATIC SEMANTICS - StringLength shall only be used with String types or to limit set of and record of. SingleExpression and Bound shall evaluate to non-negative integer values (in case of Bound including infinity) <new> and in Bound the oprional "!" shall not be present</new>*/ |
|
|
|
|
|
Pleae check the proposed solution in the previous note. |
|
|
|
|
In principle I agree, but I think it is better to exclude the exclamation mark directly in the BNF rule than by static semantics. This way we get rid off -infinity as well:
44.StringLength ::= LengthKeyword "(" SingleExpression [".." (SingleExpression | InfinityKeyword]) ")"
/* STATIC SEMANTICS - StringLength shall only be used with String types or to limit set of and record of. SingleExpression and Bound shall evaluate to non-negative integer values */ |
|
|
|
|
Yes, I agree, much better solution...
I have chenged it in the BNF <a small change: closing ) and ] shall be swapped: InfinityKeyword)] > |
|
|
|
|
|
Added to BNF in BNF tool and also to master copy. |
|
|
|
|
|