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

ID | Project | Category | View Status | Date Submitted | Last Update
0007655 | Part 01: TTCN-3 Core Language | New Feature | public | 17-03-2017 11:48 | 30-12-2017 21:44

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.9.1 (published 2017-05) |
Target Version | v4.10.1 (published 2018-05) | Fixed in Version | v4.10.1 (published 2018-05) |
Clause Reference(s) | 6.2.0, A.1.5
Source (company - Author) | Spirent - Jacob Wieland

Summary | 0007655: mixed list/assignment-notation should also be allowed for record/set types

Description

In a scenario where there exist record types with a few mandatory fields at the beginning and man optional fields at the end where in each instance, only a few of the optional fields are present, usage of the assignment-notation syntax is very useful.
However, it is tedious insofar as the names of the mandatory parameters at the beginning have to be repeated for every instance.
Thus, alike to the mixed notation for actual parameter lists, the same mixed notation with the same constraints should be allowed also for recor/set instances as well.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7655.docx (240,019) 07-06-2017 10:29 http://oldforge.etsi.org/mantis/file_download.php?file_id=3599&type=bug

Issue History
Date Modified | Username | Field | Change
17-03-2017 11:48 | Jacob Wieland - Spirent | New Issue |
18-04-2017 10:38 | szabados | Note Added: 0014568 |
18-04-2017 12:25 | Denis Filatov | File Added: a.jpg |
18-04-2017 12:26 | Denis Filatov | File Deleted: a.jpg |
18-04-2017 12:26 | Jacob Wieland - Spirent | Note Added: 0014573 |
18-04-2017 12:27 | Denis Filatov | File Added: test.txt |
18-04-2017 12:27 | Denis Filatov | File Deleted: test.txt |
06-06-2017 13:55 | Jens Grabowski | Note Added: 0014626 |
06-06-2017 13:59 | Jens Grabowski | Assigned To | => Jacob Wieland - Spirent
06-06-2017 13:59 | Jens Grabowski | Status | new => assigned
07-06-2017 10:29 | Jacob Wieland - Spirent | File Added: CR7655.docx |
07-06-2017 10:30 | Jacob Wieland - Spirent | Note Added: 0014641 |
07-06-2017 10:33 | Jacob Wieland - Spirent | Note Added: 0014642 |
07-06-2017 10:33 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Julien Deltour
07-06-2017 10:33 | Jacob Wieland - Spirent | Status | assigned => confirmed
08-06-2017 14:55 | Julien Deltour | Note Added: 0014652 |
08-06-2017 14:55 | Julien Deltour | Status | confirmed => resolved
08-06-2017 14:55 | Julien Deltour | Resolution | open => fixed
08-06-2017 14:55 | Julien Deltour | Assigned To | Julien Deltour => Gyorgy Rethy
30-12-2017 21:44 | Gyorgy Rethy | Note Added: 0014975 |
30-12-2017 21:44 | Gyorgy Rethy | Status | resolved => closed
30-12-2017 21:44 | Gyorgy Rethy | Fixed in Version | => v4.10.1 (published 2018-05)

Notes

(0014568)
szabados
18-04-2017 10:38

Just a short note, section 5.4.2 restriction b, on page 36 says: Either list notation or assignment notation shall be used in a single parameter list. They shall not be mixed. Do I remember right that it was allowed to use list notation followed by assignment notation in function calls?

(0014573)
Jacob Wieland - Spirent
18-04-2017 12:26

yes, we changed that, did we miss to delete that restriction?

(0014626)
Jens Grabowski
06-06-2017 13:55

STF discussion: agreed, check where we missed the deletion of the restriction.

(0014641)
Jacob Wieland - Spirent
07-06-2017 10:30

deleted the restriction (set to Void) changed BNF (ArrayExpression renamed to ArrayOrMixedExpression) added description and example of mixed notation also for structured values

(0014642)
Jacob Wieland - Spirent
07-06-2017 10:33

please review the proposal document

(0014652)
Julien Deltour
08-06-2017 14:55

Acceptable

(0014975)
Gyorgy Rethy
30-12-2017 21:44

Added to draft V4.9.2