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

ID | Project | Category | View Status | Date Submitted | Last Update
0006477 | Part 01: TTCN-3 Core Language | Clarification | public | 26-03-2013 10:49 | 11-07-2013 11:36

Reporter | Wolfgang Seka |
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.6.1 (published 2014-06) | Fixed in Version | v4.6.1 (published 2014-06) |
Clause Reference(s) | B.1.4.2
Source (company - Author) | MCC160 - Wolfgang

Summary | 0006477: clarification needed that it is no error to apply "ifpresent" on an expression which may result in "omit"
Description | Example var template (omit) MyType v_MyVariable := f_MyFunction(); => depending on what f_MyFunction returns v_MyVariable may result in omit; nevertheless there shall be no error for "v_MyVariable ifpresent" (i.e. "omit ifpresent" shall interpreted as omit)
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR6477.doc (157,696) 10-07-2013 16:29 http://oldforge.etsi.org/mantis/file_download.php?file_id=2818&type=bug

Issue History
Date Modified | Username | Field | Change
26-03-2013 10:49 | Wolfgang Seka | New Issue |
26-03-2013 10:49 | Wolfgang Seka | Clause Reference(s) | => B.1.4.2
26-03-2013 10:49 | Wolfgang Seka | Source (company - Author) | => MCC160 - Wolfgang
08-07-2013 14:58 | Jens Grabowski | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
08-07-2013 14:58 | Jens Grabowski | Status | new => assigned
08-07-2013 14:58 | Jens Grabowski | Assigned To | => Jacob Wieland - Spirent
08-07-2013 17:12 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2014-06)
09-07-2013 17:00 | Jacob Wieland - Spirent | Note Added: 0011487 |
10-07-2013 16:29 | Jacob Wieland - Spirent | File Added: CR6477.doc |
10-07-2013 18:14 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
10-07-2013 18:14 | Jacob Wieland - Spirent | Note Added: 0011525 |
11-07-2013 09:08 | Jacob Wieland - Spirent | Assigned To | Gyorgy Rethy => Jacob Wieland - Spirent
11-07-2013 10:15 | Jacob Wieland - Spirent | Status | assigned => confirmed
11-07-2013 10:56 | Jacob Wieland - Spirent | Status | confirmed => assigned
11-07-2013 10:56 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Ina Schieferdecker
11-07-2013 10:57 | Jacob Wieland - Spirent | Status | assigned => confirmed
11-07-2013 11:33 | Ina Schieferdecker | Status | confirmed => resolved
11-07-2013 11:33 | Ina Schieferdecker | Fixed in Version | => v4.6.1 (published 2014-06)
11-07-2013 11:33 | Ina Schieferdecker | Resolution | open => fixed
11-07-2013 11:36 | Ina Schieferdecker | Status | resolved => closed

Notes

(0011487)
Jacob Wieland - Spirent
09-07-2013 17:00

This makes sense to me. ifpresent enlarges the set of "objects" to be matched by the special value omit. If the set already contains that object, nothing happens. The same would be true if the template already is an ifpresent template or an AnyValueOrNone.
Otherwise, it would be necessary to restrict ifpresent such that it only can be applied to present-templates (thereby excluding omit, ifpresent and *). Since I don't see any harm in the idempotency of ifpresent, I would opt for allowing rather than restriction.

(0011525)
Jacob Wieland - Spirent
10-07-2013 18:14

please check