ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details
0005970Part 01: TTCN-3 Core LanguageTechnicalpublic28-11-2011 13:3130-11-2011 09:16
Tomas Urban 
Ina Schieferdecker 
normalminorN/A
closedfixed 
v4.3.1 (published 2011-06) 
v4.4.1 (published 2012-04)v4.4.1 (published 2012-04) 
20.4, restriction a
Elvior
0005970: Interleave restriction, function calls
In the chapter 20.4 (defining the interleave statement), the restriction a contains the following text:

...user-defined functions, which include communication operations, shall not be used in interleave statements.

I think "communication operations" should be replaced with "reception statements". I don't see any reason to forbid functions that e.g. send messages, because they don't affect interleave functionality. On the other hand, it seems quite strange to permit function call containg e.g. timeouts which would, if not used inside a function call, affect interleave functionality.
No tags attached.
Issue History
28-11-2011 13:31Tomas UrbanNew Issue
28-11-2011 13:31Tomas UrbanClause Reference(s) => 20.4, restriction a
28-11-2011 13:31Tomas UrbanSource (company - Author) => Elvior
28-11-2011 13:36Gyorgy RethyTarget Version => Edition 4.4.1
28-11-2011 13:54Gyorgy RethyNote Added: 0010350
28-11-2011 13:54Gyorgy RethyNote Edited: 0010350
28-11-2011 13:54Gyorgy RethyAssigned To => Ina Schieferdecker
28-11-2011 13:54Gyorgy RethyStatusnew => assigned
30-11-2011 09:15Ina SchieferdeckerNote Added: 0010413
30-11-2011 09:16Ina SchieferdeckerStatusassigned => resolved
30-11-2011 09:16Ina SchieferdeckerResolutionopen => fixed
30-11-2011 09:16Ina SchieferdeckerFixed in Version => Edition 4.4.1
30-11-2011 09:16Ina SchieferdeckerStatusresolved => closed

Notes
(0010350)
Gyorgy Rethy   
28-11-2011 13:54   
STF discussion 28/11: change "communication operations" to "reception statements".

(0010413)
Ina Schieferdecker   
30-11-2011 09:15   
as proposed.