ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0005924 | Part 01: TTCN-3 Core Language | Clarification | public | 22-08-2011 15:26 | 30-11-2011 09:42

Reporter | Andrus Lehtmets |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | major | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.4.1 (published 2012-04) | Fixed in Version | v4.4.1 (published 2012-04) |
Clause Reference(s) | TTCN-3 Edition 4.3.1: Core language
Source (company - Author) | Elvior

Summary | 0005924: What should happen when parameter list is present in port type, but not used in map operation

Description

what should happen when parameter list is present in port type, but not used in map operation:
- syntactically it is correct not to use parameters,
Specification should explicitly say if this is allowed or not from semantically point of view.
does following sentense mean that parameters must be present always when declared in port type:
"The actual parameters must conform to the map param clause of the port type declaration of the system port used"

Steps To Reproduce |

Additional Information

Ina: parameters in map, we have: â€œThe actual parameters must conform to the map param clause of the port type declaration of the system port used.â€ which means that parameter list should match the port definition.
TomÃ¡Å¡ Urban: The problem with this rule is that it you can understand it in two ways:
1. If the port type contains a map parameter declaration, the map call must contain a param clause (i.e. it cannot be omitted) and the actual parameters must be compatible with this definitition.
2. The map call might contain a param clause, in which case the actual parameters must conform to the map parameter declaration in the parent port type, but since the param clause is optional, it is allowed to skip it. (since the actual parameters are omitted, it is not possible to apply the above mentioned rule).
Notice that the same problems affects the unmap call. This one of the reasons, why we consider the second explanation more solid, because global unmap calls cannot have parametes in any case (see below). That means that unmapping calls without parameters for ports whose types contain unmap parameter declaration are perfectly legal and it would make sense to allow them even if the TSI port is explicitly referenced.

Tags | No tags attached.

Relationships

related to | 0005925 | closed | Ina Schieferdecker | in case of global unmap - is param list allowed or not?
related to | 0005923 | closed | Ina Schieferdecker | BNF (rules 50 and 58) in appendix A and port type definition chapter 6.2.9 do not match

Attached Files | CR5924-Resolution-JG-111129.doc (96,256) 29-11-2011 11:26 http://oldforge.etsi.org/mantis/file_download.php?file_id=2598&type=bug

Issue History
Date Modified | Username | Field | Change
22-08-2011 15:26 | Andrus Lehtmets | New Issue |
22-08-2011 15:26 | Andrus Lehtmets | Clause Reference(s) | => TTCN-3 Edition 4.3.1: Core language
22-08-2011 15:26 | Andrus Lehtmets | Source (company - Author) | => Elvior
27-09-2011 12:00 | Gyorgy Rethy | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
27-09-2011 12:01 | Gyorgy Rethy | Note Added: 0010246 |
27-09-2011 12:01 | Gyorgy Rethy | Assigned To | => Jens Grabowski
27-09-2011 12:01 | Gyorgy Rethy | Status | new => assigned
27-09-2011 12:01 | Gyorgy Rethy | Target Version | => Edition 4.4.1
29-11-2011 11:26 | Jens Grabowski | File Added: CR5924-Resolution-JG-111129.doc |
29-11-2011 11:28 | Jens Grabowski | Note Added: 0010384 |
29-11-2011 11:28 | Jens Grabowski | Assigned To | Jens Grabowski => Jacob Wieland - Spirent
29-11-2011 11:50 | Jacob Wieland - Spirent | Note Added: 0010386 |
29-11-2011 11:50 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Ina Schieferdecker
29-11-2011 13:55 | Jens Grabowski | Note Added: 0010395 |
29-11-2011 15:48 | Ina Schieferdecker | Relationship added | related to 0005925
29-11-2011 15:53 | Ina Schieferdecker | Relationship added | related to 0005923
30-11-2011 09:41 | Ina Schieferdecker | Note Added: 0010419 |
30-11-2011 09:41 | Ina Schieferdecker | Status | assigned => resolved
30-11-2011 09:41 | Ina Schieferdecker | Resolution | open => fixed
30-11-2011 09:41 | Ina Schieferdecker | Fixed in Version | => Edition 4.4.1
30-11-2011 09:42 | Ina Schieferdecker | Status | resolved => closed

Notes

(0010246)
Gyorgy Rethy
27-09-2011 12:01

Check possible alternatives and consistency.

(0010384)
Jens Grabowski
29-11-2011 11:28

Resolution assumes that param clauses in map operations are optional. Assigned to Jacob for cross checking.

(0010386)
Jacob Wieland - Spirent
29-11-2011 11:50

ok.

(0010395)
Jens Grabowski
29-11-2011 13:55

The resolution of this CR w.r.t. the unmap function is included in the resolution of CR5925 see file CR5925-Resolution-JW-Rev2-JG.doc.

(0010419)
Ina Schieferdecker
30-11-2011 09:41

as proposed.