Summary: | [compiler] compiled code wrong with ambiguous inner classes | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Edoardo Comar <edoardo> | ||||
Component: | Core | Assignee: | Kent Johnson <kent_johnson> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | Flags: | Olivier_Thomann:
review+
|
||||
Version: | 3.1 | ||||||
Target Milestone: | 3.3 RC1 | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Edoardo Comar
2005-02-10 09:28:15 EST
Reproduced in M6. We do not check for this scenario, and should report duplicateNestedType(memberContext) Note that a variation of this scenario is the case where MyFoo$Bar is another toplevel type, and another one when defined in a different file. The 2 cases where MyFoo$Bar is a secondary top-level type in the same file or in a different file are already detected as duplicates. Need to look into the best place to detect the member type duplicate. Created attachment 65637 [details]
Proposed patch
Now we do report a duplicate nested type as javac. Released into HEAD for 3.3 RC1 Verified for 3.3RC1 using I20070515-0010 |