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

ID | Project | Category | View Status | Date Submitted | Last Update
0005828 | Part 01: TTCN-3 Core Language | Technical | public | 28-11-2010 06:39 | 01-12-2010 14:39

Reporter | Andras Kovacs |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.3.1 (published 2011-06) | Fixed in Version | v4.3.1 (published 2011-06) |
Clause Reference(s) | [Part 1: TTCN-3 Core Language /Annex B.1.5.2 ]
Source (company - Author) | BroadBit - Andras Kovacs

Summary | 0005828: STF409 comment on [Part 1: TTCN-3 Core Language /Annex B.1.5.2 ]: syntactical ambiguity

Description

There is a contradiction between the BNF syntax for Reference expression and the examples given in the standard.
BNF Syntax:
124. CharStringMatch ::= PatternKeyword Pattern {"&" (Pattern | ReferencedValue)}
125. PatternKeyword ::= "pattern"
126. Pattern ::= """ { PatternElement } """
Quotation of examples from Annex B.1.5.2:
const charstring MyConst2 := "ab";
template charstring RegExp1 := pattern "{MyConst2}";
// matches the string "ab"
template charstring RegExp1a := pattern MyConst2;
// the same as above, matches the string "ab"
According to BNF syntax, RegExp1a assignment is not syntactically correct.

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

Relationships

related to | 0005805 | closed | Ina Schieferdecker | BNF rule for PatternElement is ambiguous, Example is wrong
related to | 0005513 | closed | Ina Schieferdecker | resolution of CR5092 contains bogus examples for charstring
related to | 0005797 | closed | Ina Schieferdecker | BNF for CharStringMatch is inconsistent with description

Attached Files |

Issue History
Date Modified | Username | Field | Change
28-11-2010 06:39 | Andras Kovacs | New Issue |
28-11-2010 06:39 | Andras Kovacs | Clause Reference(s) | => [Part 1: TTCN-3 Core Language /Annex B.1.5.2 ]
28-11-2010 06:39 | Andras Kovacs | Source (company - Author) | => BroadBit - Andras Kovacs
29-11-2010 13:06 | Jacob Wieland - Spirent | Status | new => assigned
29-11-2010 13:06 | Jacob Wieland - Spirent | Assigned To | => Jacob Wieland - Spirent
29-11-2010 13:32 | Jacob Wieland - Spirent | Note Added: 0009828 |
29-11-2010 15:51 | Jacob Wieland - Spirent | Relationship added | related to 0005797
29-11-2010 15:53 | Jacob Wieland - Spirent | Relationship added | related to 0005805
29-11-2010 15:54 | Jacob Wieland - Spirent | Relationship added | related to 0005513
30-11-2010 09:33 | Ina Schieferdecker | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
01-12-2010 10:46 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Ina Schieferdecker
01-12-2010 11:03 | Ina Schieferdecker | Note Added: 0009887 |
01-12-2010 11:03 | Ina Schieferdecker | Status | assigned => resolved
01-12-2010 11:03 | Ina Schieferdecker | Resolution | open => fixed
01-12-2010 11:03 | Ina Schieferdecker | Fixed in Version | => Edition 4.3.1 (not yet published)
01-12-2010 11:03 | Ina Schieferdecker | Target Version | => Edition 4.3.1 (not yet published)
01-12-2010 14:39 | Ina Schieferdecker | Status | resolved => closed

Notes

(0009828)
Jacob Wieland - Spirent
29-11-2010 13:32

I propose to change the BNF rule CharStringMatch ::= PatternKeyword Pattern {"&" (Pattern | ReferencedValue)} to CharStringMatch ::= PatternKeyword PatternParticle {"&" PatternParticle} PatternParticle ::= Pattern | ReferencedValue

(0009887)
Ina Schieferdecker
01-12-2010 11:03

As proposed.