| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000390 | Part 01: TTCN-3 Core Language | Clarification | public | 24-11-2006 10:01 | 12-03-2008 10:24 |
|
| Reporter | Stephan Schulz | |
| Assigned To | Ina Schieferdecker | |
| Priority | low | Severity | text | Reproducibility | N/A |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | v2.2.1 (published 2003-02) | |
| Target Version | v3.3.2 (published 2008-04) | Fixed in Version | v3.3.2 (published 2008-04) | |
|
| Summary | 0000390: Operational semantics clarification for check statement |
| Description | The current version of the core language standard defines flow control semantics for check statement in a misleading way, so that a conclusion might be drawn that the check statement has non-blocking semantics and if used as a standalone statement, it proceeds to the next statement even in case of a mismatch. Such conclusion is in conflict with TTCN-3 Operational Semantics document (Part 4 of the standard) which reasonably draws an analogy between check statement and any other receiving operation, receive statement in particular, and defines blocking semantics for check statement. |
| Additional Information | Replace the following phrase in the clause 23.4.0:
?The check operation fails if the receiving operation fails i.e. the matching criteria are not fulfilled. In this case the copy of the top element of the queue is discarded and test execution continues in the normal manner, i.e. the next statement or alternative to the check operation is evaluated.?
with:
?The check operation fails if the receiving operation fails i.e. the matching criteria are not fulfilled. In this case the copy of the top element of the queue is discarded and test execution continues in the same manner as for any other receiving operation, i.e. the next alternative to the check operation is evaluated. If check is used as a standalone statement, it has blocking semantics, i.e. it is considered to be a shorthand for an alt statement with the only one alternative.?
|
| Tags | No tags attached. |
|
| Clause Reference(s) | 23.4.0 |
| Source (company - Author) | Alexey Mednonogov, OpenTTCN Oy |
|
| Attached Files |  CR-390-Check-Statement-Resolution.doc [^] (208,384 bytes) 20-11-2007 08:04 |
|
Relationships 
Relationships 