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

ID | Project | Category | View Status | Date Submitted | Last Update
0005784 | Part 01: TTCN-3 Core Language | Clarification | public | 08-10-2010 09:45 | 30-11-2010 10:07

Reporter | Andras Kovacs |
Assigned To |  |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | no change required |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version |  | Fixed in Version |  |
Clause Reference(s) | [Part 1: TTCN-3 Core Language / Section 5.4.1.2 / restriction f) ]
Source (company - Author) | BroadBit - Andras Kovacs

Summary | 0005784: STF409 question on [Part 1: TTCN-3 Core Language / Section 5.4.1.2 / restriction f) ]
Description | Section 5.4.1.2 / restriction f) : "Default templates of default type formal parameters shall be the specific value null." This quoted restriction is not understandable to STF409 experts.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
08-10-2010 09:45 | Andras Kovacs | New Issue |
08-10-2010 09:45 | Andras Kovacs | Clause Reference(s) | => [Part 1: TTCN-3 Core Language / Section 5.4.1.2 / restriction f) ]
08-10-2010 09:45 | Andras Kovacs | Source (company - Author) | => BroadBit - Andras Kovacs
30-11-2010 09:41 | Ina Schieferdecker | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
30-11-2010 10:04 | Jacob Wieland - Spirent | Note Added: 0009836 |
30-11-2010 10:07 | Ina Schieferdecker | Status | new => closed
30-11-2010 10:07 | Ina Schieferdecker | Resolution | open => no change required

Notes

(0009836)
Jacob Wieland - Spirent
30-11-2010 10:04

First of all, you seem to reference an old version of the standard. In 4.2.1. there are no templates of type 'default' allowed anymore and restriction f) in that section is no longer containing that sentence.
However, I'll try to explain the confusing parts (as they also apply to the same restriction for formal value parameters of type default).
Probably the confusion arises from the double meaning of the word 'default' in that sentence.
The first 'default' references the concept of 'default value/template' for a formal parameter declaration. The second 'default' references the 'default' type used for handles on activated default-altsteps (for deactivation purposes).
Since there can be no global constants of type 'default' because activate() can only be called inside a behavior, the only globally known constant of type 'default' is 'null' (which can be used as a dummy initialization for variables of type 'default'). That's why it is only possible to reference that constant in a default template for a formal template parameter.
Maybe the solution would be to print the 'default' of the 'type default' in bold to distinguish them.
Anyhow, I think this can be considered closed.