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

ID | Project | Category | View Status | Date Submitted | Last Update
0005942 | Part 01: TTCN-3 Core Language | Technical | public | 05-10-2011 12:52 | 11-07-2012 11:42

Reporter | Gyorgy Rethy |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.5.1 (published 2013-04) | Fixed in Version | v4.5.1 (published 2013-04) |
Clause Reference(s) | al least 15.9
Source (company - Author) | L.M.Ericsson

Summary | 0005942: Boundness of arguments of the match operation

Description

In evolving the TTCN-3 language it has been defined that in parameters may also be partly initialized. Also, we allowed some of the operations to work on partly initialized operators. However, currently no regulation regarding boundness is included for the match operation.
Though this should be clear implicitly, it is proposed to state explicitly, as a restriction that both operators of match shall be completely initialized.
Also the standard could need sanity-check regarding other operations (the issue was raised by a user related to match and no general check could be done before sumbitting this CR).

Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

related to | 0005980 | closed | Ina Schieferdecker | all templates/variables referenced in special matching mechanism symbols shall be completely initialized

Attached Files | CR5942.doc (169,984) 29-11-2011 09:41 http://oldforge.etsi.org/mantis/file_download.php?file_id=2591&type=bug CR5942_resolution_v2.doc (54,272) 02-12-2011 10:54 http://oldforge.etsi.org/mantis/file_download.php?file_id=2655&type=bug CR5942_resolution_v3.doc (53,760) 11-07-2012 11:30 http://oldforge.etsi.org/mantis/file_download.php?file_id=2667&type=bug

Issue History
Date Modified | Username | Field | Change
05-10-2011 12:52 | Gyorgy Rethy | New Issue |
05-10-2011 12:52 | Gyorgy Rethy | Clause Reference(s) | => al least 15.9
05-10-2011 12:52 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
06-10-2011 11:44 | Gyorgy Rethy | Target Version | => Edition 4.4.1
28-11-2011 10:24 | Jacob Wieland - Spirent | Note Added: 0010333 |
28-11-2011 10:29 | Jacob Wieland - Spirent | Note Added: 0010334 |
28-11-2011 16:26 | Gyorgy Rethy | Assigned To | => Jacob Wieland - Spirent
28-11-2011 16:26 | Gyorgy Rethy | Status | new => assigned
29-11-2011 09:41 | Jacob Wieland - Spirent | File Added: CR5942.doc |
29-11-2011 09:50 | Jacob Wieland - Spirent | Note Added: 0010372 |
29-11-2011 09:51 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
02-12-2011 10:54 | Gyorgy Rethy | Note Added: 0010509 |
02-12-2011 10:54 | Gyorgy Rethy | File Added: CR5942_resolution_v2.doc |
02-12-2011 10:55 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Ina Schieferdecker
02-12-2011 10:55 | Gyorgy Rethy | Status | assigned => resolved
02-12-2011 11:10 | Jacob Wieland - Spirent | Relationship added | related to 0005980
09-07-2012 17:15 | Ina Schieferdecker | Target Version | Edition 4.4.1 => Edition 4.5.1
11-07-2012 11:30 | Ina Schieferdecker | File Added: CR5942_resolution_v3.doc |
11-07-2012 11:31 | Ina Schieferdecker | Status | resolved => closed
11-07-2012 11:31 | Ina Schieferdecker | Fixed in Version | => Edition 4.5.1
11-07-2012 11:31 | Ina Schieferdecker | Resolution | open => fixed
11-07-2012 11:42 | Ina Schieferdecker | Note Added: 0010832 |

Notes

(0010333)
Jacob Wieland - Spirent
28-11-2011 10:24

At least the section 15.11. on concatenating templates should enforce that the operands be at least partially initialized.

(0010334)
Jacob Wieland - Spirent
28-11-2011 10:29

Also, all structured matching mechanism symbols (ifpresent, subset, superset, permutation, complement, valuelist) should be restricted that their arguments should be fully initialized.

(0010372)
Jacob Wieland - Spirent
29-11-2011 09:50

uploaded proposal, the following restrictions have been added:
- parameters of match operation shall be completely initialized
- for special matching mechanism symbols (both instead-of-values and inside-values and additinal attribute symbols) containing other values or templates, these shall be completely initialized
- concatenated templates shall be completely initialized
I also added the usual structure to section 15.11

(0010509)
Gyorgy Rethy
02-12-2011 10:54

As we discussed, the user shall be able to concatenate also partially initialized values and templates.
I don't understand the matching mechanism item either. It is already defined that when a template is USED, i.e. in a sending or receiving operation, it shall be completely initialized. This, of course, also applies e.g. to the values that are members of value lists, complemented value lists etc. But why to forbid defining e.g. a var template, which has a formal parameter or a component variable in its value list? both are unidefined at the point of DEFINING the template but your restrictions could be taken as they are disallowed.
As there is an agreement regarding the match operation, I left only this in the file CR5942_resolution_v2.doc. If you still think that something should be added for the matching mechanisms, pls. submit a new CR.

(0010832)
Ina Schieferdecker
11-07-2012 11:42

Implemented as in v3