ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006688Part 06: TTCN-3 Control InterfaceTechnicalpublic07-02-2014 06:4726-01-2015 11:37
ReporterIna Schieferdecker 
Assigned ToTomas Urban 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versionv4.5.1 (published 2013-04) 
Target Versionv4.7.1 (published 2015-06)Fixed in Versionv4.7.1 (published 2015-06) 
Clause Reference(s)various
Source (company - Author)Ina Schieferdecker, FOKUS
Summary0006688: Log and TLI should support modifiers
Description@index, @lazy, @fuzzy and @deterministic have been added recently into part 1, but not into TLI or into the log statement.

As e.g. fuzzy or lazy are rather tricky I see the need to enable logging of the current modifier features of a variable, etc.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filesdocx CR6688_v1.docx (424,969) 19-06-2014 13:58
http://oldforge.etsi.org/mantis/file_download.php?file_id=3058&type=bug
Issue History
Date ModifiedUsernameFieldChange
07-02-2014 06:47Ina SchieferdeckerNew Issue
07-02-2014 06:47Ina SchieferdeckerClause Reference(s) => various
07-02-2014 06:47Ina SchieferdeckerSource (company - Author) => Ina Schieferdecker, FOKUS
08-04-2014 11:24Gyorgy RethyAssigned To => Jens Grabowski
08-04-2014 11:24Gyorgy RethyStatusnew => assigned
08-04-2014 11:24Gyorgy RethyTarget Version => v4.7.1 (published 2015-06)
30-04-2014 09:38Jacob Wieland - SpirentNote Added: 0012061
07-05-2014 13:37Jacob Wieland - SpirentNote Added: 0012065
17-06-2014 07:38Jens GrabowskiAssigned ToJens Grabowski => Tomas Urban
18-06-2014 16:20Tomas UrbanNote Added: 0012132
19-06-2014 13:58Tomas UrbanFile Added: CR6688_v1.docx
19-06-2014 13:59Tomas UrbanNote Added: 0012144
19-06-2014 13:59Tomas UrbanAssigned ToTomas Urban => Jens Grabowski
19-06-2014 13:59Tomas UrbanStatusassigned => confirmed
06-10-2014 10:58Jens GrabowskiNote Added: 0012225
06-10-2014 10:59Jens GrabowskiAssigned ToJens Grabowski => Tomas Urban
06-10-2014 10:59Jens GrabowskiStatusconfirmed => assigned
06-10-2014 11:23Tomas UrbanNote Added: 0012227
06-10-2014 11:23Tomas UrbanStatusassigned => resolved
06-10-2014 11:23Tomas UrbanResolutionopen => fixed
17-12-2014 09:40Tomas UrbanNote Added: 0012558
17-12-2014 09:40Tomas UrbanStatusresolved => closed
26-01-2015 11:37Gyorgy RethyFixed in Version => v4.7.1 (published 2015-06)

Notes
(0012061)
Jacob Wieland - Spirent   
30-04-2014 09:38   
It is also a little bit unclear when the tliVar log event shall occur in case of lazy/fuzzy variables. If it shall occur at assignment of the variable, what would the logged value be (as it not to be evaluated)? In my opinion, the tliVar should be delayed to the time of actual evaluation of the variable. In case of fuzzy variables, it could be called whenever the variable is evaluated.
(0012065)
Jacob Wieland - Spirent   
07-05-2014 13:37   
Another interesting question is what the logging should do with initialized-but-unevaluated lazy/fuzzy variables/parameters (i.e. in tliLog, tliSEnter, tliSLeave).
(0012132)
Tomas Urban   
18-06-2014 16:20   
Proposal:
@deterministic shall be hadled as a special kind of scope, i.e. the current string parameter "kind" of the tliSEnter and tliSLeave shall contain "@deterministic function" instead of just "function". This way the signature of these calls will remain backwards compatible.

@index doesn't require special handling, as redirect assignments don't have dedicated parameters in the TLI receiving calls and the index of the actual port is available through the at parameter.

@fuzzy and not evaluated @lazy values will be represented by a special TCI value objects. This way the TCI interface prevents the users from examining the value details. The tliVar will always use these objects in case of @fuzzy and @lazy variable assignments and they can appear in tliSEnter, tliSLeave and other parameterized calls as well.

The specification will also define a new dedicated tliVarEvaluate call that occurs every time when a value of @fuzzy or @lazy variable is calculated.
(0012144)
Tomas Urban   
19-06-2014 13:59   
Proposal uploaded, assigned to Jens for cross-checking.
(0012225)
Jens Grabowski   
06-10-2014 10:58   
Proposal is fine with me.
(0012227)
Tomas Urban   
06-10-2014 11:23   
Ready for adding into the standard.
(0012558)
Tomas Urban   
17-12-2014 09:40   
Added to the TCI specification draft 4.6.2.