Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004703Part 01: TTCN-3 Core LanguageClarificationpublic15-01-2009 14:2601-07-2009 15:10
ReporterIna Schieferdecker 
Assigned ToIna Schieferdecker 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Versionv4.2.1 (published 2010-07)Fixed in Versionv4.2.1 (published 2010-07) 
Summary0004703: Explaination of standalone receive
DescriptionPart 1 explains for Stand-alone receive:

The receive operation can be used as a stand-alone statement in a behaviour description. In this latter case the receive operation is considered to be shorthand for an alt statement with only one alternative, i.e. it has blocking semantics, and therefore provides the ability of waiting for the next message matching the specified template or value on that queue.

The latter part on "waiting for the next message matching the specified template" can be misinterpreted, so that not only the top level messages can be matched.

This is not true. The blocking semantics holds.

Hence, a simplification is proposed to

"The receive operation can be used as a stand-alone statement in a behaviour description. In this latter case the receive operation is considered to be shorthand for an alt statement with only one alternative."

which removes the confusing part and makes clear, that the semantics of an alt statement applies
TagsNo tags attached.
Clause Reference(s)22.2.2
Source (company - Author)Wolfgang Seka, MCC160
Attached Filesdoc file icon CR-4703-Explaination-of-standalone-receive-JG.doc [^] (203,264 bytes) 21-04-2009 12:02

- Relationships

-  Notes
(0008522)
Jens Grabowski (manager)
21-04-2009 10:39

The "confusing part" is used for the description of several stand-alone statements (e.g., done, trigger, timeout, killed). The simplification should be done for all statements/operations.
(0008525)
Jens Grabowski (manager)
21-04-2009 12:03

Proposal for resolution uploaded. Assigned to Ina for crosschecking.
(0008807)
Ina Schieferdecker (reporter)
01-07-2009 15:09

Included as proposed.

- Issue History
Date Modified Username Field Change
15-01-2009 14:26 Ina Schieferdecker New Issue
15-01-2009 14:26 Ina Schieferdecker Clause Reference(s) => 22.2.2
15-01-2009 14:26 Ina Schieferdecker Source (company - Author) => Wolfgang Seka, MCC160
15-01-2009 14:27 Ina Schieferdecker Project TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
15-01-2009 14:27 Ina Schieferdecker Assigned To => Jens Grabowski
15-01-2009 14:27 Ina Schieferdecker Status new => assigned
15-01-2009 14:27 Ina Schieferdecker Category TTCN-3 Core Language => Clarification
15-01-2009 14:27 Ina Schieferdecker Target Version => Edition 4.2.1 (not yet published)
21-04-2009 10:39 Jens Grabowski Note Added: 0008522
21-04-2009 12:02 Jens Grabowski File Added: CR-4703-Explaination-of-standalone-receive-JG.doc
21-04-2009 12:03 Jens Grabowski Note Added: 0008525
21-04-2009 12:03 Jens Grabowski Assigned To Jens Grabowski => Ina Schieferdecker
01-07-2009 15:09 Ina Schieferdecker Note Added: 0008807
01-07-2009 15:09 Ina Schieferdecker Resolution open => fixed
01-07-2009 15:10 Ina Schieferdecker Status assigned => resolved
01-07-2009 15:10 Ina Schieferdecker Fixed in Version => Edition 4.2.1 (not yet published)
01-07-2009 15:10 Ina Schieferdecker Status resolved => closed


MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker