ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000390Part 01: TTCN-3 Core LanguageClarificationpublic24-11-2006 10:0112-03-2008 10:24
ReporterStephan Schulz 
Assigned ToIna Schieferdecker 
PrioritylowSeveritytextReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versionv2.2.1 (published 2003-02) 
Target Versionv3.3.2 (published 2008-04)Fixed in Versionv3.3.2 (published 2008-04) 
Clause Reference(s)23.4.0
Source (company - Author)Alexey Mednonogov, OpenTTCN Oy
Summary0000390: Operational semantics clarification for check statement
DescriptionThe 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.
Steps To Reproduce
Additional InformationReplace 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.?
TagsNo tags attached.
Relationships
Attached Filesdoc CR-390-Check-Statement-Resolution.doc (208,384) 20-11-2007 08:04
http://oldforge.etsi.org/mantis/file_download.php?file_id=1128&type=bug
Issue History
Date ModifiedUsernameFieldChange
24-11-2006 10:01Stephan SchulzNew Issue
24-11-2006 10:01Stephan SchulzClause Reference(s) => 23.4.0
24-11-2006 10:01Stephan SchulzSource (company - Author) => Alexey Mednonogov, OpenTTCN Oy
24-11-2006 10:02Stephan SchulzNote Added: 0000309
24-11-2006 10:02Stephan SchulzStatusnew => confirmed
15-06-2007 19:19Stephan SchulzStatusconfirmed => assigned
15-06-2007 19:19Stephan SchulzAssigned To => Ina Schieferdecker
13-10-2007 19:14Ina SchieferdeckerAssigned ToIna Schieferdecker => Jens Grabowski
18-10-2007 14:29Ina SchieferdeckerTarget Version => Edition 3.3.1 (not yet published)
18-10-2007 14:29Ina SchieferdeckerAdditional Information Updated
20-11-2007 08:04Jens GrabowskiFile Added: CR-390-Check-Statement-Resolution.doc
20-11-2007 08:05Jens GrabowskiAssigned ToJens Grabowski => Gyorgy Rethy
20-11-2007 08:05Jens GrabowskiResolutionopen => fixed
05-12-2007 11:41Jens GrabowskiAssigned ToGyorgy Rethy => Ina Schieferdecker
05-12-2007 11:41Jens GrabowskiStatusassigned => resolved
05-12-2007 17:41Ina SchieferdeckerStatusresolved => closed
05-12-2007 17:41Ina SchieferdeckerFixed in Version => Edition 3.3.1 (not yet published)
12-03-2008 10:22user10Fixed in VersionEdition 3.3.1 --will not be published, see 3.3.2 => Edition 3.3.2 (not yet published)
12-03-2008 10:24user10Target VersionEdition 3.3.1 --will not be published, see 3.3.2 => Edition 3.3.2 (not yet published)

Notes
(0000309)
Stephan Schulz   
24-11-2006 10:02   
Accepted