ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006423Part 01: TTCN-3 Core LanguageTechnicalpublic18-02-2013 11:1928-08-2013 16:49
ReporterTomas Urban 
Assigned ToIna Schieferdecker 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Versionv4.6.1 (published 2014-06)Fixed in Versionv4.6.1 (published 2014-06) 
Clause Reference(s)16.1.4
Source (company - Author)Elvior
Summary0006423: Restriction on communication operations in functions
DescriptionThe chapter 16.1.4 states that "Value returning functions can be called in communication operations... To avoid side effects that cause changing the state of the component or the actual snapshot and to prevent different results of subsequent evaluations on an unchanged snapshot, the following operations shall not be used in functions called in the cases specified above."

I think the use of the expression "communication operations" is misfortunate and puts unnecessary restrictions on non-blocking operations. Operations like send, getcall etc. are never a part of snaphot evaluation. Therefore I suggest to change "communication operations" to "blocking communication operations".
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0006511closed Ina Schieferdecker One more "special place" for function call 
related to 0006422closed Ina Schieferdecker Restrictions on operations invoked from special places 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
18-02-2013 11:19Tomas UrbanNew Issue
18-02-2013 11:19Tomas UrbanClause Reference(s) => 16.1.4
18-02-2013 11:19Tomas UrbanSource (company - Author) => Elvior
08-07-2013 15:40Jens GrabowskiProjectTTCN-3 Change Requests => Part 01: TTCN-3 Core Language
08-07-2013 15:43Jens GrabowskiRelationship addedrelated to 0006511
08-07-2013 15:43Jens GrabowskiStatusnew => assigned
08-07-2013 15:43Jens GrabowskiAssigned To => Jacob Wieland - Spirent
08-07-2013 15:44Jens GrabowskiRelationship addedrelated to 0006422
08-07-2013 18:15Gyorgy RethyTarget Version => v4.6.1 (published 2014-06)
09-07-2013 11:38Jacob Wieland - SpirentNote Added: 0011457
09-07-2013 16:12Jacob Wieland - SpirentNote Added: 0011484
10-07-2013 15:30Jacob Wieland - SpirentNote Added: 0011506
11-07-2013 10:19Jacob Wieland - SpirentStatusassigned => confirmed
11-07-2013 10:48Jacob Wieland - SpirentStatusconfirmed => assigned
11-07-2013 10:48Jacob Wieland - SpirentAssigned ToJacob Wieland - Spirent => Ina Schieferdecker
28-08-2013 16:49Ina SchieferdeckerStatusassigned => resolved
28-08-2013 16:49Ina SchieferdeckerResolutionopen => fixed
28-08-2013 16:49Ina SchieferdeckerFixed in Version => v4.6.1 (published 2014-06)
28-08-2013 16:49Ina SchieferdeckerStatusresolved => closed

Notes
(0011457)
Jacob Wieland - Spirent   
09-07-2013 11:38   
How about: "operations invoked during snapshot evaluation"?
(0011484)
Jacob Wieland - Spirent   
09-07-2013 16:12   
Actually, it should simply be disallowed to directly or indirectly call functions containing implicit or explicit alt statements (and all blocking operations written on their own are implicit alt statements) from the snapshot-evaluation part of an alt statement (i.e the guard or the event part).
(0011506)
Jacob Wieland - Spirent   
10-07-2013 15:30   
resolution proposal see CR6511