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

ID | Project | Category | View Status | Date Submitted | Last Update
0007453 | Part 01: TTCN-3 Core Language | Technical | public | 18-07-2016 15:58 | 13-12-2016 10:14

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.9.1 (published 2017-05) | Fixed in Version | v4.9.1 (published 2017-05) |
Clause Reference(s) | 27.7, 6.2.1.0
Source (company - Author) | STF 514

Summary | 0007453: Restriction on use of optional attibutes in variables
Description | According to the restriction 27.7.a, optional attributes cannot be used for variables. However, there are two examples in the standard which don't follow this restriction (in 6.2.1.0). Proposal: Either lift the restriction and add the rules for a single field assignment (see 0007288 for more details) or keep the restriction as it is and correct the examples.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

related to | 0007288 | closed | Gyorgy Rethy | Not described use cases for optional attribute

Attached Files | CR7453_proposal.docx (156,091) 17-11-2016 12:36 http://oldforge.etsi.org/mantis/file_download.php?file_id=3554&type=bug CR7453_proposal_v2.docx (178,251) 17-11-2016 14:35 http://oldforge.etsi.org/mantis/file_download.php?file_id=3557&type=bug

Issue History
Date Modified | Username | Field | Change
18-07-2016 15:58 | Tomas Urban | New Issue |
18-07-2016 15:59 | Tomas Urban | Relationship added | related to 0007288
19-07-2016 15:36 | Tomas Urban | Assigned To | => KristÃ³f Szabados
19-07-2016 15:36 | Tomas Urban | Status | new => assigned
19-07-2016 15:40 | Tomas Urban | Note Added: 0013991 |
22-07-2016 13:48 | KristÃ³f Szabados | Note Added: 0014038 |
17-08-2016 11:31 | Jacob Wieland - Spirent | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
17-08-2016 11:55 | Jacob Wieland - Spirent | Target Version | => v4.9.1 (published 2017-05)
17-11-2016 12:00 | KristÃ³f Szabados | Status | assigned => confirmed
17-11-2016 12:36 | KristÃ³f Szabados | File Added: CR7453_proposal.docx |
17-11-2016 12:36 | KristÃ³f Szabados | Note Added: 0014301 |
17-11-2016 12:36 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Tomas Urban
17-11-2016 12:36 | KristÃ³f Szabados | Status | confirmed => assigned
17-11-2016 14:35 | Tomas Urban | File Added: CR7453_proposal_v2.docx |
17-11-2016 14:40 | Tomas Urban | Note Added: 0014312 |
17-11-2016 14:40 | Tomas Urban | Assigned To | Tomas Urban => KristÃ³f Szabados
17-11-2016 14:40 | Tomas Urban | Status | assigned => confirmed
17-11-2016 15:27 | KristÃ³f Szabados | Status | confirmed => resolved
17-11-2016 15:27 | KristÃ³f Szabados | Fixed in Version | => v4.9.1 (published 2017-05)
17-11-2016 15:27 | KristÃ³f Szabados | Resolution | open => fixed
17-11-2016 15:27 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Gyorgy Rethy
13-12-2016 10:14 | Gyorgy Rethy | Note Added: 0014402 |
13-12-2016 10:14 | Gyorgy Rethy | Status | resolved => closed

Notes

(0013991)
Tomas Urban
19-07-2016 15:40

STF discussion: It seems feasible to allow the optional attribute for variables, but it could cause backwards compatibility problems as global implicit omit (e.g. on module level) would affect all variables now. The impact is probably minimal, but it depends on test suites. A question should be sent to vendors and STF 160 if the proposed change affects them anyhow.

(0014038)
KristÃ³f Szabados
22-07-2016 13:48

Please note, that this CR is related to CR 7288. If this limitation is lifted (and optional attributes can be attached to variables) it should be defined what the behaviour will be like in the 2nd case of CR 7288.

(0014301)
KristÃ³f Szabados
17-11-2016 12:36

please review

(0014312)
Tomas Urban
17-11-2016 14:40

The proposal was mostly OK. However I made some changes: 1. I moved the rule on assignments out of the restriction section, because in fact it is not a restriction, but description of the feature. 2. I made small changes in wording of the moved rule and the note. 3. I fixed some wording in the examples Please check and mark as resolved if you find no more issues.

(0014402)
Gyorgy Rethy
13-12-2016 10:14

Added to draft V4.8.2