| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0005365 | Part 01: TTCN-3 Core Language | Technical | public | 23-09-2009 18:09 | 16-02-2010 07:00 |
|
| Reporter | Anthony Baire | |
| Assigned To | Ina Schieferdecker | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | v4.1.1 (published 2009-06) | |
| Target Version | v4.2.1 (published 2010-07) | Fixed in Version | v4.2.1 (published 2010-07) | |
|
| Summary | 0005365: [BNF] various issues in ValueSpec |
| Description | The new definition of ValueSpec has several issues:
- it is not consistent with the textual description of the feature in 22.2.2
- it is too loose (and thus not easy to parse)
- the presence of TypeDefIdentifier is superfluous because this rule is already included by FieldReference
ValueSpec ::= ValueKeyword ( VariableRef | "(" { [ VariableRef [ AssignmentChar (FieldReference | TypeDefIdentifier) ExtendedFieldReference ] ] [","] } ")" )
Suggested replacement:
ValueSpec ::= ValueKeyword ( VariableRef | "(" SingleValueSpec { "," SingleValueSpec } ")" )
SingleValueSpec ::= VariableRef [ AssignmentChar FieldReference ExtendedFieldReference ]
|
| Tags | No tags attached. |
|
| Clause Reference(s) | A.1.6.2.4 |
| Source (company - Author) | |
|
| Attached Files | |
|
Relationships 
Relationships 