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

ID | Project | Category | View Status | Date Submitted | Last Update
0003943 | Part 01: TTCN-3 Core Language | Technical | public | 10-08-2008 12:31 | 17-08-2008 10:07

Reporter | Gyorgy Rethy |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | always
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) | $6.2.10.2
Source (company - Author) | L.M.Ericsson

Summary | 0003943: Ambiguity in component type extension

Description

Name clashes between the parent and the children comp. types are disallowed but the standard leaves ambiguity if names are clashing between the definitions in the different parent types (used in the same step of extension). E.g. in the case of
type component X { timer T1:=1.0}
type component Y { timer T1:=2.0}
type component Z extends X,Y { timer T2; }
function f() runs on Z {
T1.start
}
what is the initial duration of timer T1?

Steps To Reproduce |

Additional Information

Add a new restriction b) in $6.2.10.2 (shift existing b) to c)):
b) When defining component types by extending more than one parent types, there shall be no name clash between the definitions of the different parent types, i.e. there shall not be a port, variable, constant or timer identifier that is declared in any two of the parent types (directly or by means of extension).

Tags | No tags attached.
Relationships |
Attached Files | CR_3943_ambiguity_in_component_extension_resolution_01.doc (159,744) 13-08-2008 10:32 http://oldforge.etsi.org/mantis/file_download.php?file_id=1590&type=bug

Issue History
Date Modified | Username | Field | Change
10-08-2008 12:31 | Gyorgy Rethy | New Issue |
10-08-2008 12:31 | Gyorgy Rethy | Status | new => assigned
10-08-2008 12:31 | Gyorgy Rethy | Assigned To | => Ina Schieferdecker
10-08-2008 12:31 | Gyorgy Rethy | Clause Reference(s) | => $6.2.10.2
10-08-2008 12:31 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
11-08-2008 08:50 | Ina Schieferdecker | Note Added: 0006476 |
11-08-2008 08:51 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Thomas DeiÃŸ
13-08-2008 10:32 | Thomas DeiÃŸ | File Added: CR_3943_ambiguity_in_component_extension_resolution_01.doc |
13-08-2008 10:34 | Thomas DeiÃŸ | Note Added: 0006509 |
13-08-2008 10:34 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Gyorgy Rethy
13-08-2008 10:34 | Thomas DeiÃŸ | Resolution | open => fixed
15-08-2008 11:01 | Gyorgy Rethy | Note Added: 0006542 |
15-08-2008 11:01 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Ina Schieferdecker
15-08-2008 11:01 | Gyorgy Rethy | Status | assigned => resolved
17-08-2008 09:02 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
17-08-2008 10:07 | Ina Schieferdecker | Status | resolved => closed
17-08-2008 10:07 | Ina Schieferdecker | Fixed in Version | => Edition 4.1.1 (not yet published)

Notes

(0006476)
Ina Schieferdecker
11-08-2008 08:50

agreed in principle, but allow the diamond case for component type extension

(0006509)
Thomas DeiÃŸ
13-08-2008 10:34

resolution proposal for checking added.

(0006542)
Gyorgy Rethy
15-08-2008 11:01

Resolution proposal checked, OK from my side.