ETSI's Bug Tracker - Part 01: TTCN-3 Core Language |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006645 | Part 01: TTCN-3 Core Language | Editorial | public | 17-10-2013 16:32 | 04-01-2015 19:05 |
|
| Reporter | Tomas Urban | |
| Assigned To | Gyorgy Rethy | |
| Priority | low | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | v4.7.1 (published 2015-06) | Fixed in Version | v4.7.1 (published 2015-06) | |
| Clause Reference(s) | 6.2.3, 6.2.7 |
| Source (company - Author) | STF 470 |
|
| Summary | 0006645: Rules for array values |
| Description | 6.2.3 contains several references to array values. However, since the chapter is only about record of and set of, such references shouldn't be there, because the specification has a dedicated section for arrays (6.2.7). I believe that specifying rules for different language elements than those the chapter is about should be avoided at all costs. Otherwise the specification loses readability. The reference to array is also quite misleading and unnecessary in case of an index notation, because arrays have their own rules that are slightly different from the rules for record of and set of.
I propose the following editorial changes:
1. Remove all occurrences of the word "array" from 6.2.3.
2. 6.2.7 has a rule saying that the allowed notation for is the index notation and value list notation, but assignment notation is not mentioned in this rule: "Values may be assigned individually by a value list notation or indexed notation or more than one or all at once by a value list notation". However, since 6.2 already specifies general rules for using the value list and assignment notations and further rules in 6.2.7 state that the index notation is also a valid option, I think the rule is superfluous and can be dropped.
3. Since 6.2.7 doesn't contain any rules for using the assignment notation for arrays, these rules shall be added to 6.2.7, either by saying that rules described in 6.2.3 are valid for arrays as well or putting a slightly adjusted version of these rules into the chapter 6.2.7.
|
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | 0006762 | closed | Gyorgy Rethy | Array indexing breaches strong typing principle | | related to | 0006646 | closed | Gyorgy Rethy | Missing semantic rules for the index and assignment notation |
|
| Attached Files |  draft-res-6645-v1.docx (30,803) 04-11-2014 17:35
http://oldforge.etsi.org/mantis/file_download.php?file_id=3162&type=bug
draft-res-6645-v2.docx (33,954) 05-11-2014 09:47
http://oldforge.etsi.org/mantis/file_download.php?file_id=3165&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 17-10-2013 16:32 | Tomas Urban | New Issue | |
| 17-10-2013 16:32 | Tomas Urban | Clause Reference(s) | => 6.2.3, 6.2.7 |
| 17-10-2013 16:32 | Tomas Urban | Source (company - Author) | => STF 470 |
| 21-11-2013 16:51 | Gyorgy Rethy | Note Added: 0011814 | |
| 22-11-2013 14:49 | Gyorgy Rethy | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language |
| 22-11-2013 14:50 | Gyorgy Rethy | Note Edited: 0011814 | |
| 22-11-2013 14:50 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2014-06) |
| 22-11-2013 14:51 | Gyorgy Rethy | Status | new => assigned |
| 22-11-2013 14:51 | Gyorgy Rethy | Assigned To | => Ina Schieferdecker |
| 29-11-2013 12:53 | Ina Schieferdecker | Note Added: 0011868 | |
| 29-11-2013 12:54 | Ina Schieferdecker | Target Version | v4.6.1 (published 2014-06) => v4.7.1 (published 2015-06) |
| 08-04-2014 16:51 | Gyorgy Rethy | Assigned To | Ina Schieferdecker => Gyorgy Rethy |
| 06-10-2014 14:52 | Gyorgy Rethy | Priority | normal => low |
| 10-10-2014 08:30 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Axel Rennoch |
| 04-11-2014 17:35 | Axel Rennoch | File Added: draft-res-6645-v1.docx | |
| 04-11-2014 17:38 | Axel Rennoch | Note Added: 0012409 | |
| 05-11-2014 08:53 | Axel Rennoch | Assigned To | Axel Rennoch => Tomas Urban |
| 05-11-2014 08:53 | Axel Rennoch | Status | assigned => confirmed |
| 05-11-2014 09:46 | Tomas Urban | Relationship added | related to 0006762 |
| 05-11-2014 09:46 | Tomas Urban | Relationship added | related to 0006646 |
| 05-11-2014 09:47 | Tomas Urban | File Added: draft-res-6645-v2.docx | |
| 05-11-2014 09:50 | Tomas Urban | Note Added: 0012416 | |
| 05-11-2014 09:50 | Tomas Urban | Assigned To | Tomas Urban => Axel Rennoch |
| 05-11-2014 10:17 | Axel Rennoch | Note Added: 0012419 | |
| 05-11-2014 10:18 | Axel Rennoch | Note Added: 0012420 | |
| 05-11-2014 10:18 | Axel Rennoch | Assigned To | Axel Rennoch => Tomas Urban |
| 05-11-2014 10:18 | Axel Rennoch | Status | confirmed => acknowledged |
| 05-11-2014 14:28 | Tomas Urban | Note Added: 0012435 | |
| 05-11-2014 14:28 | Tomas Urban | Status | acknowledged => resolved |
| 05-11-2014 14:28 | Tomas Urban | Fixed in Version | => v4.7.1 (published 2015-06) |
| 05-11-2014 14:28 | Tomas Urban | Resolution | open => fixed |
| 05-11-2014 14:28 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy |
| 04-01-2015 19:05 | Gyorgy Rethy | Note Added: 0012606 | |
| 04-01-2015 19:05 | Gyorgy Rethy | Status | resolved => closed |
|
Notes |
|
|
(0011814)
|
|
Gyorgy Rethy
|
21-11-2013 16:51
(edited on: 22-11-2013 14:50) |
|
This structure has more a historical reason than technical. Once we have agreed that - with some minor technical deviations (e.g. array indexing may start with other index than 0, but don't have a named type) - arrays and length restricted record of-s are equivalent. For this reason clauses 6.2.3 and 6.2.7 could be merged, but we will not have time to do this at our last session in 2014 next week. I propose a quick patch now to handle the index assignment notation issue and open a follow-up CR to make the merge. Let discuss this at the STF session next week.
|
|
|
|
|
In response to issue 2, changed in 6.2.7
"Values may be assigned individually by a value list notation or indexed notation or more than one or all at once by a value list notation."
to
"Values may be assigned individually by a value list notation or indexed notation or more than one or all at once by a value list notation or index assignment notation."
The suggested rewrites will be done in 2014 only. |
|
|
|
|
|
Minimal changes to solve issues 1 and 3 as well as some font/typo corrections are provided with the uploaded draft resolution v1. We still may do a bigger change, i.e. merging 6.2.3 and 6.2.7. |
|
|
|
|
I am fine with the changes, but I added several more rules to the array section in order to make sure that no rules are lost because of the removal of references to arrays from the section 6.2.3.
Please review the updated proposal. |
|
|
|
|
|
Thank you, the changes are fine for me. :-) |
|
|
|
|
|
Can you set the status to "resolved"? |
|
|
|
|
|
The proposed changes have been reviewed and can be added to the next verion of the TTCN-3 core language standard. |
|
|
|
|
|