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

ID | Project | Category | View Status | Date Submitted | Last Update
0007472 | Part 01: TTCN-3 Core Language | New Feature | public | 08-08-2016 15:37 | 16-12-2016 19:25

Reporter | Jacob Wieland - Spirent |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.8.1 (published 2016-07) |
Target Version | v4.9.1 (published 2017-05) | Fixed in Version | v4.9.1 (published 2017-05) |
Clause Reference(s) | 5.4.2
Source (company - Author) | Spirent - Jacob Wieland

Summary | 0007472: mixed parameter-style lists should be allowed

Description

Normally, a paramterized entity has some mandatory parameters and possibly some optional ones. The mandatory are usually declared first in the formal parameter list and the optional ones later.
Other languages like, for instance, Python allow the user to give the actual parameter list in a mixed style, where you would put first the parameters with a fixed place (i.e. the mandatory ones) and then can add additional ones in the named-parameter-style (i.e. assignment notation).
This way, the user does not have to remember and over-and-over again write down the mandatory parameter names, but only has to write down what is absolutely necessary while still being concise.

Steps To Reproduce | take the following function header function f(T1 mp1, ..., Tn mpn, O1 op1 := d1, ..., Om opm := dm); The instances of this function should be allowed to look like this: f(a1,...,an,opi := oai, opj := oaj)
Additional Information |
Tags | No tags attached.

Relationships

related to | 0007492 | closed | Gyorgy Rethy | duplication and ambiguity concerning actual par lists in BNF

Attached Files | CR7472.docx (236,213) 16-08-2016 13:16 http://oldforge.etsi.org/mantis/file_download.php?file_id=3461&type=bug

Issue History
Date Modified | Username | Field | Change
08-08-2016 15:37 | Jacob Wieland - Spirent | New Issue |
15-08-2016 10:49 | Jens Grabowski | Note Added: 0014067 |
15-08-2016 10:50 | Jens Grabowski | Assigned To | => Jacob Wieland - Spirent
15-08-2016 10:50 | Jens Grabowski | Status | new => assigned
16-08-2016 12:07 | Jacob Wieland - Spirent | Relationship added | related to 0007492
16-08-2016 13:16 | Jacob Wieland - Spirent | File Added: CR7472.docx |
16-08-2016 13:16 | Jacob Wieland - Spirent | Note Added: 0014107 |
16-08-2016 13:16 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Tomas Urban
16-08-2016 13:16 | Jacob Wieland - Spirent | Status | assigned => confirmed
17-08-2016 10:27 | Tomas Urban | Note Added: 0014124 |
17-08-2016 10:27 | Tomas Urban | Status | confirmed => resolved
17-08-2016 10:27 | Tomas Urban | Resolution | open => fixed
17-08-2016 10:27 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
17-08-2016 10:38 | Jacob Wieland - Spirent | Assigned To | Gyorgy Rethy => Jacob Wieland - Spirent
17-08-2016 10:38 | Jacob Wieland - Spirent | Status | resolved => feedback
17-08-2016 10:38 | Jacob Wieland - Spirent | Resolution | fixed => reopened
17-08-2016 10:42 | Jacob Wieland - Spirent | Note Added: 0014126 |
17-08-2016 10:42 | Jacob Wieland - Spirent | Status | feedback => assigned
17-08-2016 10:42 | Jacob Wieland - Spirent | Status | assigned => resolved
17-08-2016 10:42 | Jacob Wieland - Spirent | Resolution | reopened => fixed
17-08-2016 10:42 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
17-08-2016 11:20 | Jacob Wieland - Spirent | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
17-08-2016 11:20 | Jacob Wieland - Spirent | Status | resolved => feedback
17-08-2016 11:20 | Jacob Wieland - Spirent | Resolution | fixed => reopened
17-08-2016 11:20 | Jacob Wieland - Spirent | Product Version | => v4.8.1 (published 2016-07)
17-08-2016 11:20 | Jacob Wieland - Spirent | Target Version | => v4.9.1 (published 2017-05)
17-08-2016 11:21 | Jacob Wieland - Spirent | Status | feedback => resolved
17-08-2016 11:21 | Jacob Wieland - Spirent | Fixed in Version | => v4.9.1 (published 2017-05)
17-08-2016 11:21 | Jacob Wieland - Spirent | Resolution | reopened => fixed
13-12-2016 08:38 | Gyorgy Rethy | Note Added: 0014401 |
13-12-2016 08:40 | Gyorgy Rethy | Status | resolved => feedback
13-12-2016 08:40 | Gyorgy Rethy | Resolution | fixed => reopened
14-12-2016 13:11 | Jacob Wieland - Spirent | Note Added: 0014435 |
14-12-2016 13:11 | Jacob Wieland - Spirent | Status | feedback => assigned
16-12-2016 19:25 | Gyorgy Rethy | Note Added: 0014449 |
16-12-2016 19:25 | Gyorgy Rethy | Status | assigned => closed
16-12-2016 19:25 | Gyorgy Rethy | Resolution | reopened => fixed

Notes

(0014067)
Jens Grabowski
15-08-2016 10:49

STF discussion: resonable extension, Jacob prepares proposal.

(0014107)
Jacob Wieland - Spirent
16-08-2016 13:16

please review

(0014124)
Tomas Urban
17-08-2016 10:27

Proposal is ready to be included into the next version of the core language specification.

(0014126)
Jacob Wieland - Spirent
17-08-2016 10:42

please add a version number to this CR, if it is possible

(0014401)
Gyorgy Rethy
13-12-2016 08:38

Added to draft V4.8.2 with the addition to the new restriction m): "no value list notation shall be used following the first assignment notation"
The whole restriction is now:
"m) If the mixed notation is used, no value list notation shall be used following the first assignment notation and the parameters given in assignment notation shall not assign parameters that already have an actual parameter given in list notation."
This is in line with the intention of the CR and the first paragraph of clause 5.4.2, but defines a formal rule for this requirement (otherwise we should define the semantics of a pure parameter value between two parameters with assignment notation).
Please notify me if you disagree.

(0014435)
Jacob Wieland - Spirent
14-12-2016 13:11

Perfect!

(0014449)
Gyorgy Rethy
16-12-2016 19:25

Added to draft V4.8.2