ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006688 | Part 06: TTCN-3 Control Interface | Technical | public | 07-02-2014 06:47 | 26-01-2015 11:37

Reporter | Ina Schieferdecker |
Assigned To | Tomas Urban |
Priority | normal | Severity | minor | Reproducibility | have not tried
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) | various
Source (company - Author) | Ina Schieferdecker, FOKUS

Summary | 0006688: 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 |
Tags | No tags attached.
Relationships |
Attached Files | 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 Modified | Username | Field | Change
07-02-2014 06:47 | Ina Schieferdecker | New Issue |
07-02-2014 06:47 | Ina Schieferdecker | Clause Reference(s) | => various
07-02-2014 06:47 | Ina Schieferdecker | Source (company - Author) | => Ina Schieferdecker, FOKUS
08-04-2014 11:24 | Gyorgy Rethy | Assigned To | => Jens Grabowski
08-04-2014 11:24 | Gyorgy Rethy | Status | new => assigned
08-04-2014 11:24 | Gyorgy Rethy | Target Version | => v4.7.1 (published 2015-06)
30-04-2014 09:38 | Jacob Wieland - Spirent | Note Added: 0012061 |
07-05-2014 13:37 | Jacob Wieland - Spirent | Note Added: 0012065 |
17-06-2014 07:38 | Jens Grabowski | Assigned To | Jens Grabowski => Tomas Urban
18-06-2014 16:20 | Tomas Urban | Note Added: 0012132 |
19-06-2014 13:58 | Tomas Urban | File Added: CR6688_v1.docx |
19-06-2014 13:59 | Tomas Urban | Note Added: 0012144 |
19-06-2014 13:59 | Tomas Urban | Assigned To | Tomas Urban => Jens Grabowski
19-06-2014 13:59 | Tomas Urban | Status | assigned => confirmed
06-10-2014 10:58 | Jens Grabowski | Note Added: 0012225 |
06-10-2014 10:59 | Jens Grabowski | Assigned To | Jens Grabowski => Tomas Urban
06-10-2014 10:59 | Jens Grabowski | Status | confirmed => assigned
06-10-2014 11:23 | Tomas Urban | Note Added: 0012227 |
06-10-2014 11:23 | Tomas Urban | Status | assigned => resolved
06-10-2014 11:23 | Tomas Urban | Resolution | open => fixed
17-12-2014 09:40 | Tomas Urban | Note Added: 0012558 |
17-12-2014 09:40 | Tomas Urban | Status | resolved => closed
26-01-2015 11:37 | Gyorgy Rethy | Fixed 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.