#1918 closed defect (fixed)
Implement better checking of extends in new instantiation
Reported by: | perost | Owned by: | perost |
---|---|---|---|
Priority: | low | Milestone: | 1.9.4 |
Component: | New Instantiation | Version: | trunk |
Keywords: | Cc: |
Description
Extends are currently fully qualified in the new instantiation, since they may not be redeclared. We should do this in a better way so that we can detect if any part of the path is replaceable. We should also check the restriction that extended classes shouldn't be found in any of the extends in the scope while doing the qualifying, so we can avoid doing that the rest of the time and simplify the lookup.
Change History (3)
comment:1 Changed 11 years ago by perost
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 8 years ago by dietmarw
- Milestone changed from Future to pre1.9.4
comment:3 Changed 6 years ago by sjoelund.se
- Milestone changed from pre1.9.4 to 1.9.4
Removing the pre1.9.4 milestone in favor of 1.9.4.
It doesn't make sense to keep closed ticket in the "Future" milestone that were simply forgotten to assign to the correct milestone in the past.