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
0005786Part 01: TTCN-3 Core LanguageClarificationpublic08-10-2010 09:5114-12-2010 12:20
ReporterAndras Kovacs 
Assigned ToIna Schieferdecker 
PrioritynormalSeverityminorReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Versionv4.3.1 (published 2011-06)Fixed in Versionv4.3.1 (published 2011-06) 
Summary0005786: STF409 question on [Part 1: TTCN-3 Core Language / Section 6.3.4 ]
DescriptionThe content of section 6.3.4 is not clear. Specific issues:
- The given example is incomplete, because the port definitions are missing.
- It is not clear what happens when a communications port is defined to process the messages of a given record type as well as its type synonym.
 
TagsNo tags attached.
Clause Reference(s)[Part 1: TTCN-3 Core Language / Section 6.3.4 ]
Source (company - Author)BroadBit - Andras Kovacs
Attached Filesdoc file icon CR5786.doc [^] (29,696 bytes) 01-12-2010 09:07

- Relationships

-  Notes
(0009781)
Jacob Wieland - Spirent (reporter)
14-10-2010 11:09

In the example, it is stated (albeit in a comment) that the port can process (i.e. send/receive) both types (contrary to your stated point 2). Since the ports are connected (not mapped, where the situation is a bit more difficult because of encoding/decoding), the sent type must be exactly the same as the type of the template to be received (not just compatible) so that matching occurs on the receive statement. This is what the whole section is about. So, the example is in essence complete.

However, the example is still wrong in two respects (in my opinion):
- P2.receive(MyRec:?) shall not cause an error, but simply a mismatch (there could be other or default alternatives that receive MyRecAlias)
- P2.receive(MyRec:?) -> value x shall also not cause an error, as - again - this is simply a mismatch and thus no assignment shall take place. And even if an assignment would take place, assigning of a value of one type to a variable of a different type is well defined using the weaker type compatibility rules (but since there will be no matching here, this point is moot - however, in a mapped port, this could be valid).
(0009859)
Gyorgy Rethy (reporter)
30-11-2010 16:15
edited on: 30-11-2010 16:15

STF discussion on 30-11-2010: add the port type definition to the example. Also fix Jacob's findings.

(0009871)
Jacob Wieland - Spirent (reporter)
01-12-2010 09:08

please proofread
(0009876)
Jens Grabowski (manager)
01-12-2010 09:50

Ok, status is set to resolved and CR is assigned to Ina.
(0009962)
Ina Schieferdecker (reporter)
14-12-2010 12:19

Implemented as proposed

- Issue History
Date Modified Username Field Change
08-10-2010 09:51 Andras Kovacs New Issue
08-10-2010 09:51 Andras Kovacs Clause Reference(s) => [Part 1: TTCN-3 Core Language / Section 6.3.4 ]
08-10-2010 09:51 Andras Kovacs Source (company - Author) => BroadBit - Andras Kovacs
14-10-2010 11:09 Jacob Wieland - Spirent Note Added: 0009781
30-11-2010 09:40 Ina Schieferdecker Project TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
30-11-2010 16:15 Gyorgy Rethy Note Added: 0009859
30-11-2010 16:15 Gyorgy Rethy Note Edited: 0009859
30-11-2010 16:16 Gyorgy Rethy Assigned To => Jacob Wieland - Spirent
30-11-2010 16:16 Gyorgy Rethy Status new => assigned
30-11-2010 16:16 Gyorgy Rethy Target Version => Edition 4.3.1 (not yet published)
01-12-2010 09:07 Jacob Wieland - Spirent File Added: CR5786.doc
01-12-2010 09:08 Jacob Wieland - Spirent Note Added: 0009871
01-12-2010 09:08 Jacob Wieland - Spirent Assigned To Jacob Wieland - Spirent => Jens Grabowski
01-12-2010 09:50 Jens Grabowski Note Added: 0009876
01-12-2010 09:51 Jens Grabowski Assigned To Jens Grabowski => Ina Schieferdecker
01-12-2010 09:51 Jens Grabowski Status assigned => resolved
14-12-2010 12:19 Ina Schieferdecker Note Added: 0009962
14-12-2010 12:19 Ina Schieferdecker Resolution open => fixed
14-12-2010 12:19 Ina Schieferdecker Fixed in Version => Edition 4.3.1 (not yet published)
14-12-2010 12:20 Ina Schieferdecker Status resolved => closed


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