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
0006718Part 01: TTCN-3 Core LanguageTechnicalpublic09-04-2014 13:4405-01-2015 18:31
ReporterTomas Urban 
Assigned ToGyorgy Rethy 
PrioritynormalSeverityminorReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versionv4.6.1 (published 2014-06) 
Target Versionv4.7.1 (published 2015-06)Fixed in Versionv4.7.1 (published 2015-06) 
Summary0006718: Null value in the to and from clause
DescriptionAddress values can contain a special value null (see 6.2.12 for more details). However, it is not obvious what would happen if this value is used in the communication operations. In my opinion there are two options:

1. It will produce an error.
2. It will work: in case of outgoing operation, no address will be passed to the SA (the corresponding field of the TRI operation will be null). It would be just a more verbous variant of outgoing operations without a to clause. In case of an incoming operation, using null in the from clause would mean that the event can be accepted only if the SA didn't supply any address. (This is different than omitting the from clause as the sender address is not matched in this case).
TagsNo tags attached.
Clause Reference(s)22
Source (company - Author)STF 478
Attached Filesdocx file icon CR6718_resolution_v1.docx [^] (94,500 bytes) 06-10-2014 16:38
zip file icon Operational-Semantics-CR6718.zip [^] (1,618,357 bytes) 07-10-2014 14:07

- Relationships

-  Notes
(0012236)
Gyorgy Rethy (reporter)
06-10-2014 16:06
edited on: 06-10-2014 16:08

 Shall cause an error. Jens to check if this is already included in Part-4 (if the receiver cannot be determined, it should cause an error).
(0012238)
Gyorgy Rethy (reporter)
06-10-2014 16:38

 Please check CR6718_resolution_v1.docx.
(0012241)
Jens Grabowski (manager)
07-10-2014 08:24

 Resolution is fine with me. Will also be implemented in OS.
(0012253)
Jens Grabowski (manager)
07-10-2014 14:07

 CR also implemented in operational semantics.
(0012629)
Gyorgy Rethy (reporter)
05-01-2015 18:31

 Added to draft V4.6.3

- Issue History
Date Modified Username Field Change
09-04-2014 13:44 Tomas Urban New Issue
18-06-2014 08:38 Gyorgy Rethy Project TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
18-06-2014 08:38 Gyorgy Rethy Product Version => v4.6.1 (published 2014-06)
18-06-2014 08:38 Gyorgy Rethy Target Version => v4.7.1 (published 2015-06)
06-10-2014 16:06 Gyorgy Rethy Note Added: 0012236
06-10-2014 16:06 Gyorgy Rethy Assigned To => Gyorgy Rethy
06-10-2014 16:06 Gyorgy Rethy Status new => confirmed
06-10-2014 16:08 Gyorgy Rethy Note Edited: 0012236 View Revisions
06-10-2014 16:38 Gyorgy Rethy File Added: CR6718_resolution_v1.docx
06-10-2014 16:38 Gyorgy Rethy Note Added: 0012238
06-10-2014 16:39 Gyorgy Rethy Assigned To Gyorgy Rethy => Jens Grabowski
07-10-2014 08:24 Jens Grabowski Note Added: 0012241
07-10-2014 08:24 Jens Grabowski Status confirmed => resolved
07-10-2014 08:24 Jens Grabowski Resolution open => fixed
07-10-2014 08:24 Jens Grabowski Assigned To Jens Grabowski => Gyorgy Rethy
07-10-2014 08:24 Jens Grabowski Status resolved => assigned
07-10-2014 08:25 Jens Grabowski Status assigned => resolved
07-10-2014 14:07 Jens Grabowski File Added: Operational-Semantics-CR6718.zip
07-10-2014 14:07 Jens Grabowski Note Added: 0012253
05-01-2015 18:31 Gyorgy Rethy Note Added: 0012629
05-01-2015 18:31 Gyorgy Rethy Status resolved => closed
05-01-2015 18:31 Gyorgy Rethy Fixed in Version => v4.7.1 (published 2015-06)

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