Logo etsi

ETSI's Bug Tracker
Main | My View | View Issues | Change Log | Roadmap | Monitor project
  
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
0005925Part 01: TTCN-3 Core LanguageTechnicalpublic22-08-2011 15:3030-11-2011 10:29
ReporterAndrus Lehtmets 
Assigned ToIna Schieferdecker 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Versionv4.4.1 (published 2012-04)Fixed in Versionv4.4.1 (published 2012-04) 
Summary0005925: in case of global unmap - is param list allowed or not?
Descriptionin case of global unmap - are param list allowed or not
Ex.

unmap(all component:all port) param (...);

Syntactically it is allowed, but semantically it does not make sense.
Additional InformationIna: parameters in unmap, there is a point as TTCN-3 indeed seems not to be explicit here … I am thinking that both cases for a PortRef make sense, i.e. no parameter list or a matching one.

Tomáš Urban: we agree with that. We also think that the rule "The actual parameters must conform to the unmap param clause of the port type declaration of the system port used" semantically forbids use of the param clause if any of the "all port" construction is used, because there's no system port explicitly used in the clause.

Thus, in order to avoid any possible ambiguity, we would prefer to update the syntax so that the param clause is syntactically allowed only with the first two variants:
unmap [ ( "(" ComponentRef ":" Port "," ComponentRef ":" Port ")" [ param "(" [ { ActualPar [","] }+ ] ")" ] ) |
             ( "(" PortRef ")" [ param "(" [ { ActualPar [","] }+ ] ")" ] ) |
             ( "(" ComponentRef ":" all port ")" ) |
             ( "(" all component ":" all port ")" ) ]

There's also a problem with the unmap call containing one parameter. If the parameter is not a TSI port, but a mapped test component port, the call doesn't contain an explicit TSI port reference, but it can be found from the list of current mappings. The question is if such an implicit reference satisfies the above mentioned rule. In our opinion, it does not. Thus, we would prefer to add the rule that the param clause can be present only if a system port is explicitly referenced in the unmap call.
TagsNo tags attached.
Clause Reference(s)TTCN-3 Edition 4.3.1: Core language
Source (company - Author)Elvior
Attached Filesdoc file icon CR5925-Resolution-JG-111129.doc [^] (196,608 bytes) 29-11-2011 10:58
doc file icon CR5925-Resolution-JW.doc [^] (116,224 bytes) 29-11-2011 11:34
doc file icon CR5925-Resolution-JW-Rev2-JG.doc [^] (146,944 bytes) 29-11-2011 13:51
doc file icon CR5925-Resolution-JW-Rev2-JG-3.doc [^] (134,144 bytes) 30-11-2011 10:17

- Relationships
related to 0005923closedIna Schieferdecker BNF (rules 50 and 58) in appendix A and port type definition chapter 6.2.9 do not match 
related to 0005924closedIna Schieferdecker What should happen when parameter list is present in port type, but not used in map operation 

-  Notes
(0010245)
Gyorgy Rethy (reporter)
27-09-2011 11:55

 To be analysed.
(0010380)
Jens Grabowski (manager)
29-11-2011 10:59

 Resolution proposal follows the proposal in the Additional Information description. Assigned to Jacob for cross checking.
(0010385)
Jacob Wieland - Spirent (reporter)
29-11-2011 11:35

 removed typo

deleted unused (inlined) BNF rule, replaced by new rule ParamClause which is used for both map and unmap (to avoid repetition)
(0010394)
Jens Grabowski (manager)
29-11-2011 13:53

 The file CR5925-Resolution-JW-Rev2-JG.doc includes restrictions related to CR5924.
(0010423)
Ina Schieferdecker (reporter)
30-11-2011 10:17

 implemented with small correction in the BNF

- Issue History
Date Modified Username Field Change
22-08-2011 15:30 Andrus Lehtmets New Issue
22-08-2011 15:30 Andrus Lehtmets Clause Reference(s) => TTCN-3 Edition 4.3.1: Core language
22-08-2011 15:30 Andrus Lehtmets Source (company - Author) => Elvior
27-09-2011 11:55 Gyorgy Rethy Note Added: 0010245
27-09-2011 11:55 Gyorgy Rethy Assigned To => Jens Grabowski
27-09-2011 11:55 Gyorgy Rethy Status new => assigned
27-09-2011 11:55 Gyorgy Rethy Project TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
27-09-2011 13:28 Gyorgy Rethy Target Version => Edition 4.4.1
29-11-2011 10:58 Jens Grabowski File Added: CR5925-Resolution-JG-111129.doc
29-11-2011 10:59 Jens Grabowski Note Added: 0010380
29-11-2011 11:00 Jens Grabowski Assigned To Jens Grabowski => Jacob Wieland - Spirent
29-11-2011 11:34 Jacob Wieland - Spirent File Added: CR5925-Resolution-JW.doc
29-11-2011 11:35 Jacob Wieland - Spirent Note Added: 0010385
29-11-2011 11:46 Jacob Wieland - Spirent Assigned To Jacob Wieland - Spirent => Ina Schieferdecker
29-11-2011 13:51 Jens Grabowski File Added: CR5925-Resolution-JW-Rev2-JG.doc
29-11-2011 13:53 Jens Grabowski Note Added: 0010394
29-11-2011 15:48 Ina Schieferdecker Relationship added related to 0005924
29-11-2011 15:54 Ina Schieferdecker Relationship added related to 0005923
30-11-2011 10:17 Ina Schieferdecker Note Added: 0010423
30-11-2011 10:17 Ina Schieferdecker File Added: CR5925-Resolution-JW-Rev2-JG-3.doc
30-11-2011 10:29 Ina Schieferdecker Status assigned => resolved
30-11-2011 10:29 Ina Schieferdecker Resolution open => fixed
30-11-2011 10:29 Ina Schieferdecker Fixed in Version => Edition 4.4.1
30-11-2011 10:29 Ina Schieferdecker Status resolved => closed

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