ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details
0005866Part 01: TTCN-3 Core LanguageClarificationpublic03-03-2011 18:1001-07-2011 17:32
Wolfgang Seka 
Jacob Wieland - Spirent 
highminorhave not tried
closedfixed 
v4.1.1 (published 2009-06) 
v4.3.2 (interim 2011)v4.3.2 (interim 2011) 
ES 201 873-1 cl. 22
stf160 - Wolfgang
0005866: Unspecified behaviour when ports not being connected are used in communication operations
Currently it is not clear from TTCN-3 core language what happens when a communication operation is applied to a port which is not connected or mapped.
Especially for send events clarification is needed.
It seems that the operational semantics (part 4) specifies a runtime error at least for send events on not connected ports.
But other interpretations/solutions may be valid as well => clarification is needed to achieve tool compatibility.

Especially for receive statements there is no obvious reason from a user's point of view why a runtime error shall be raise when a not connected port is used in an alt statement.

Note: apart from the necessary clarification this issue may be related to CR 005243
No tags attached.
doc CR5866-Resolution-110526.doc (140,800) 26-05-2011 12:22
http://oldforge.etsi.org/mantis/file_download.php?file_id=2500&type=bug
Issue History
03-03-2011 18:10Wolfgang SekaNew Issue
03-03-2011 18:10Wolfgang SekaClause Reference(s) => ES 201 873-1 cl. 22
03-03-2011 18:10Wolfgang SekaSource (company - Author) => stf160 - Wolfgang
24-05-2011 14:44Gyorgy RethyNote Added: 0010019
24-05-2011 14:45Gyorgy RethyAssigned To => Jens Grabowski
24-05-2011 14:45Gyorgy RethyStatusnew => assigned
24-05-2011 14:45Gyorgy RethyFixed in Version => Edition 4.3.2 (interim)
24-05-2011 19:10Gyorgy RethyFixed in VersionEdition 4.3.2 (interim) =>
24-05-2011 19:10Gyorgy RethyTarget Version => Edition 4.3.2 (interim)
24-05-2011 19:18Gyorgy RethyPrioritynormal => high
24-05-2011 19:18Gyorgy RethyCategoryTechnical => Clarification
26-05-2011 11:55Jens GrabowskiFile Added: CR5866-Resolution-110526.doc
26-05-2011 11:56Jens GrabowskiNote Added: 0010079
26-05-2011 11:56Jens GrabowskiAssigned ToJens Grabowski => Jacob Wieland - Spirent
26-05-2011 12:22Jacob Wieland - SpirentFile Deleted: CR5866-Resolution-110526.doc
26-05-2011 12:22Jacob Wieland - SpirentFile Added: CR5866-Resolution-110526.doc
26-05-2011 12:22Jacob Wieland - SpirentNote Added: 0010082
26-05-2011 12:23Jacob Wieland - SpirentStatusassigned => resolved
26-05-2011 12:23Jacob Wieland - SpirentResolutionopen => fixed
01-07-2011 17:30Ina SchieferdeckerNote Added: 0010199
01-07-2011 17:32Ina SchieferdeckerStatusresolved => closed
01-07-2011 17:32Ina SchieferdeckerFixed in Version => Edition 4.3.2 (interim)

Notes
(0010019)
Gyorgy Rethy   
24-05-2011 14:44   
Shall cause an error. Check the standard's text and add a clarification if needed.
(0010079)
Jens Grabowski   
26-05-2011 11:56   
Assigned to Jacob for proofreading
(0010082)
Jacob Wieland - Spirent   
26-05-2011 12:22   
replaced with a version with a few typos fixed. Otherwise OK.
(0010199)
Ina Schieferdecker   
01-07-2011 17:30   
Implemented as proposed.