ETSI's Bug Tracker - Part 05: TTCN-3 Runtime Interface
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006683 | Part 05: TTCN-3 Runtime Interface | Technical | public | 06-02-2014 07:44 | 19-12-2014 09:07

Reporter | Tomas Urban |
Assigned To | Tomas Urban |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.5.1 (published 2013-04) |
Target Version | v4.7.1 (published 2015-06) | Fixed in Version | v4.7.1 (published 2015-06) |
Clause Reference(s) | 5.5.2
Source (company - Author) | Elvior

Summary | 0006683: triUnmapParam call invoked when unmap operation has just one parameter

Description

The current TRI specification doesn't provide any guidelines for the situation when a parameterized unmap call contains a system port that is mapped to more than one component port. Will there be one triUnmapParam call for the first (or last) component port and common triUnmap calls for the remaining ones? Or will there be triUnmapParam calls for all of them and the values of out parameters will be taken from the first (or last) call?

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | Question_for_TTCN-3_tool_vendors_CR6683.txt (1,620) 14-04-2014 08:56 http://oldforge.etsi.org/mantis/file_download.php?file_id=3021&type=bug CR6683_v1.docx (49,354) 16-06-2014 14:57 http://oldforge.etsi.org/mantis/file_download.php?file_id=3033&type=bug CR6683_v2.docx (49,411) 08-10-2014 11:15 http://oldforge.etsi.org/mantis/file_download.php?file_id=3109&type=bug

Issue History
Date Modified | Username | Field | Change
06-02-2014 07:44 | Tomas Urban | New Issue |
06-02-2014 07:44 | Tomas Urban | Clause Reference(s) | => 5.5.2
06-02-2014 07:44 | Tomas Urban | Source (company - Author) | => Elvior
08-04-2014 11:14 | Gyorgy Rethy | Note Added: 0011957 |
08-04-2014 11:14 | Gyorgy Rethy | Assigned To | => Tomas Urban
08-04-2014 11:14 | Gyorgy Rethy | Status | new => assigned
08-04-2014 11:14 | Gyorgy Rethy | Target Version | => v4.7.1 (published 2015-06)
11-04-2014 10:17 | Tomas Urban | Note Added: 0012021 |
14-04-2014 08:53 | Gyorgy Rethy | File Added: Question for TTCN-3 tool vendors CR6683.txt |
14-04-2014 08:54 | Gyorgy Rethy | Note Added: 0012033 |
14-04-2014 08:56 | Gyorgy Rethy | File Deleted: Question for TTCN-3 tool vendors CR6683.txt |
14-04-2014 08:56 | Gyorgy Rethy | File Added: Question_for_TTCN-3_tool_vendors_CR6683.txt |
15-04-2014 09:11 | Jacob Wieland - Spirent | Note Added: 0012034 |
16-06-2014 14:57 | Tomas Urban | File Added: CR6683_v1.docx |
16-06-2014 14:58 | Tomas Urban | Note Added: 0012089 |
16-06-2014 14:58 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
16-06-2014 14:58 | Tomas Urban | Status | assigned => confirmed
17-06-2014 07:19 | Jacob Wieland - Spirent | Note Added: 0012094 |
08-10-2014 11:15 | Gyorgy Rethy | File Added: CR6683_v2.docx |
08-10-2014 11:15 | Gyorgy Rethy | Note Added: 0012275 |
08-10-2014 11:15 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Tomas Urban
08-10-2014 11:15 | Gyorgy Rethy | Status | confirmed => resolved
08-10-2014 11:15 | Gyorgy Rethy | Resolution | open => fixed
08-10-2014 11:15 | Gyorgy Rethy | Fixed in Version | => v4.7.1 (published 2015-06)
19-12-2014 09:07 | Tomas Urban | Note Added: 0012565 |
19-12-2014 09:07 | Tomas Urban | Status | resolved => closed

Notes

(0011957)
Gyorgy Rethy
08-04-2014 11:14

Ask other tool vendors how this case has been solved.

(0012021)
Tomas Urban
11-04-2014 10:17

Question to TTCN-3 tool vendors send. Answers expected by the beginning of June.

(0012033)
Gyorgy Rethy
14-04-2014 08:54

Tomas's mail is uploaded as file attachment.

(0012034)
Jacob Wieland - Spirent
15-04-2014 09:11

For Testing Tech, the only consistent semantics is that an
unmap(c:p) param(p1,...,pn)
is equivalent to
foreach (mc:mp | mc:mp is mapped to c:p) {
unmap(c:p, mc:mp) param(p1, ..., pn)
}
That means that there will be a triUnmapParam call for each mapped port (preferably in the order that they were originally mapped to make it unambiguous)
which also induces a semantics for the inout/out parameters of the unmap param declaration (i.e. if a parameter is an out parameter, the last triUnmapParam call which assigns it a value 'wins', if it is an inout parameter, subsequent assignments to the parameter are done for each triUnmapParam call).

(0012089)
Tomas Urban
16-06-2014 14:58

I added a proposal based on the algorithm described by Jacob. A similar change was made for the triUnmap function. Please check

(0012094)
Jacob Wieland - Spirent
17-06-2014 07:19

fine with me

(0012275)
Gyorgy Rethy
08-10-2014 11:15

OK, one typo is corrected in CR6683_v2.docx.

(0012565)
Tomas Urban
19-12-2014 09:07

Proposed change added to the specification draft.