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

ID | Project | Category | View Status | Date Submitted | Last Update
0005803 | Part 01: TTCN-3 Core Language | Technical | public | 10-11-2010 14:06 | 14-12-2010 11:57

Reporter | Andras Kovacs |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.3.1 (published 2011-06) | Fixed in Version | v4.3.1 (published 2011-06) |
Clause Reference(s) | Part 1: TTCN-3 Core Language / Section 19.11
Source (company - Author) | BroadBit - Andras Kovacs

Summary | 0005803: STF409 comment on [Part 1: TTCN-3 Core Language / Section 19.11 ]: ad-hoc restrictions

Description

The following list is given for restrictions on the 'log' statement:
"Functions used in log statements shall not use directly or indirectly statements other than ifâ€¦else, for, while, doâ€¦while, label, goto, return, mtc, system, self, running (PTC or timer), read and getverdict."
This list seems rather ad-hoc. For example if for/while operations are allowed, then why 'break' operation is not allowed? Since if-else is allowed, why select-case is not allowed? It is recommended to revise these restrictions.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
10-11-2010 14:06 | Andras Kovacs | New Issue |
10-11-2010 14:06 | Andras Kovacs | Clause Reference(s) | => Part 1: TTCN-3 Core Language / Section 19.11
10-11-2010 14:06 | Andras Kovacs | Source (company - Author) | => BroadBit - Andras Kovacs
11-11-2010 13:49 | Jacob Wieland - Spirent | Note Added: 0009795 |
30-11-2010 09:35 | Ina Schieferdecker | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
30-11-2010 16:53 | Gyorgy Rethy | Note Added: 0009863 |
30-11-2010 16:53 | Gyorgy Rethy | Assigned To | => Ina Schieferdecker
30-11-2010 16:53 | Gyorgy Rethy | Status | new => assigned
30-11-2010 16:53 | Gyorgy Rethy | Target Version | => Edition 4.3.1 (not yet published)
01-12-2010 17:12 | Ina Schieferdecker | Note Added: 0009908 |
01-12-2010 17:12 | Ina Schieferdecker | Note Added: 0009909 |
01-12-2010 17:12 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Gyorgy Rethy
01-12-2010 17:13 | Ina Schieferdecker | Status | assigned => resolved
01-12-2010 17:13 | Ina Schieferdecker | Resolution | open => fixed
01-12-2010 17:13 | Ina Schieferdecker | Fixed in Version | => Edition 4.3.1 (not yet published)
02-12-2010 10:20 | Gyorgy Rethy | Status | resolved => feedback
02-12-2010 10:20 | Gyorgy Rethy | Resolution | fixed => reopened
02-12-2010 10:20 | Gyorgy Rethy | Note Added: 0009920 |
02-12-2010 10:21 | Gyorgy Rethy | Note Added: 0009921 |
02-12-2010 10:21 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Ina Schieferdecker
02-12-2010 10:21 | Gyorgy Rethy | Status | feedback => resolved
02-12-2010 10:21 | Gyorgy Rethy | Resolution | reopened => fixed
14-12-2010 11:57 | Ina Schieferdecker | Status | resolved => closed

Notes

(0009795)
Jacob Wieland - Spirent
11-11-2010 13:49

Why is any restriction necessary anyway? Why can't I log the result of a function which starts some ptcs, waits for their results and the computes its result in return? This just forces me to put that result in a variable and then log that variable instead? Where is the gain?

(0009863)
Gyorgy Rethy
30-11-2010 16:53

STF discussion 30-11-2010: remove the restriction of the log statement

(0009908)
Ina Schieferdecker
01-12-2010 17:12

Restrictions redefined from
----------
In addition to the general static rules of TTCN 3 given in clause 5, the following restrictions apply:
a) Functions used in log statements shall not use directly or indirectly statements other than ifâ€¦else, for, while, doâ€¦while, label, goto, return, mtc, system, self, running (PTC or timer), read and getverdict.
----------
to
----------
No specific restrictions in addition to the general static rules of TTCN 3 given in clause 5.
----------
In addition, rewording of shall into should not. From
----------
It is strongly recommended that the execution of the log statement has no effect on the test behaviour. In particular, functions used in a log statement shall neither explicitly nor implicitly change component variable values, port or timer status, and shall not change the value of any of its inout or out parameters.
----------
to
----------
It is strongly recommended that the execution of the log statement has no effect on the test behaviour. In particular, functions used in a log statement should not (explicitly or implicitly) change component variable values, port or timer status, and should not change the value of any of its inout or out parameters.
----------

(0009909)
Ina Schieferdecker
01-12-2010 17:12

Please check.

(0009920)
Gyorgy Rethy
02-12-2010 10:20

Shall reopen to be able to assign to Ina.

(0009921)
Gyorgy Rethy
02-12-2010 10:21

OK with me.