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

ID | Project | Category | View Status | Date Submitted | Last Update
0006011 | Part 01: TTCN-3 Core Language | Clarification | public | 03-02-2012 14:42 | 10-07-2012 13:36

Reporter | Gyorgy Rethy |
Assigned To |  |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | won't fix |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.5.1 (published 2013-04) | Fixed in Version |  |
Clause Reference(s) | 8.2.3.5
Source (company - Author) | L.M.Ericsson

Summary | 0006011: Wording of the restriction (dont mix all import with selective import) doesn't make sense

Description

In clause 8.2.3.5, Restriction a) is: "If all visible definitions of a module are imported by using the all keyword, no other form of import (import of single definitions, import of the same kind, etc.) shall be used for the same import statement."
The BNF doesn't allow mixing import-all and selective import in the same statement.
import from A all {type all} //syntactically disallowed
Therefore the restriction doesn't make sense today.
Solution:
a) delete "for the same import statement"
b) change "for the same import statement" to "for the same import-from module"
c) delete the whole restriction.
pls. note, that due to import-of-imports, this shall remain to be allowed:
import from A all;
import from A {import all}
that syntactically looks very similar to a sequence of an import-all and a selective import satements:
import from A all;
import from A {template all}
therefore solution c) seems to be the most user-friendly.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
03-02-2012 14:42 | Gyorgy Rethy | New Issue |
03-02-2012 14:42 | Gyorgy Rethy | Clause Reference(s) | => 8.2.3.5
03-02-2012 14:42 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
19-04-2012 11:31 | Jacob Wieland - Spirent | Note Added: 0010558 |
10-07-2012 13:36 | Gyorgy Rethy | Note Added: 0010753 |
10-07-2012 13:36 | Gyorgy Rethy | Status | new => closed
10-07-2012 13:36 | Gyorgy Rethy | Resolution | open => won't fix
10-07-2012 13:36 | Gyorgy Rethy | Target Version | => Edition 4.5.1

Notes

(0010558)
Jacob Wieland - Spirent
19-04-2012 11:31

The BNF simply implements the restriction. So, it is consistent with the restriction. I don't see the problem. Arguing with a sequence of multiple import statements against a restriction which only restricts single import statements doesn't make sense to me, either.

(0010753)
Gyorgy Rethy
10-07-2012 13:36

Leave as is to make the difference between importing the dedfinitions and the import statements visible.