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

ID | Project | Category | View Status | Date Submitted | Last Update
0003382 | Part 01: TTCN-3 Core Language | Clarification | public | 16-05-2008 10:07 | 18-07-2008 10:54

Reporter | Thomas DeiÃŸ |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version | v4.1.1 (published 2009-06) |
Clause Reference(s) | 8.2.3
Source (company - Author) | Nokia Siemens Networks, Thomas DeiÃŸ

Summary | 0003382: cyclic import

Description

Clause 8.2.3 states that cyclic imports are forbidden.
It is unclear whether the example below qualifies as cyclic import.
module a {
import from b { type x }
type record of x list_x;
}
module b {
type integer x;
import from a { type list_x }
}
I suggest to add a sentence to 8.2.3 that the cycles are considered on module level:
"Cyclic imports are forbidden. Cycles are determined on module level"

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

Issue History
Date Modified | Username | Field | Change
16-05-2008 10:07 | Thomas DeiÃŸ | New Issue |
16-05-2008 10:07 | Thomas DeiÃŸ | Status | new => assigned
16-05-2008 10:07 | Thomas DeiÃŸ | Assigned To | => Ina Schieferdecker
16-05-2008 10:07 | Thomas DeiÃŸ | Clause Reference(s) | => 8.2.3
16-05-2008 10:07 | Thomas DeiÃŸ | Source (company - Author) | => Nokia Siemens Networks, Thomas DeiÃŸ
14-07-2008 15:23 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Jens Grabowski
15-07-2008 16:20 | Jens Grabowski | Note Added: 0006285 |
16-07-2008 09:37 | Jens Grabowski | Assigned To | Jens Grabowski => Thomas DeiÃŸ
18-07-2008 08:44 | Thomas DeiÃŸ | Note Added: 0006319 |
18-07-2008 08:44 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Ina Schieferdecker
18-07-2008 08:44 | Thomas DeiÃŸ | Resolution | open => fixed
18-07-2008 10:41 | Ina Schieferdecker | Status | assigned => closed
18-07-2008 10:41 | Ina Schieferdecker | Fixed in Version | => Edition 4.1.1 (not yet published)
18-07-2008 10:41 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
18-07-2008 10:54 | Ina Schieferdecker | File Added: CR-3379-Resolution-JG-TD-IS-080719.doc |
18-07-2008 10:55 | Ina Schieferdecker | File Deleted: CR-3379-Resolution-JG-TD-IS-080719.doc |

Notes

(0006285)
Jens Grabowski
15-07-2008 16:20

Proposal for resolution:
Delete restriction "h) Cyclic imports are forbidden" in Clause 8.2.3.1.
Reasons:
- The original reason for introducing this restriction was to avoid cyclic definitions. However, the problem of cyclic definitions has to be solved on module level. See CR 3379
- Furthermore, originally the cyclic imports restriction was meant to work on definition level but could be misinterpreted as a restriction on module level. For example:
module A imports const B-const of type integer from Module B
module B imports const A-const of type integer from Module A
can be interpretet as a cyclic import on module level (module A imports from B and B imports from A), but causes no problems at all.

(0006319)
Thomas DeiÃŸ
18-07-2008 08:44

Proposed solution (see previous note) is ok.