Bug 220039 - [1.5][compiler] Compiler incorrectly detects a cycle in the type hierarhcy
Summary: [1.5][compiler] Compiler incorrectly detects a cycle in the type hierarhcy
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: 3.4 M6   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-22 16:33 EST by John Williams CLA
Modified: 2008-03-26 03:05 EDT (History)
3 users (show)

See Also:


Attachments
A project that demonstrates the problem. (615 bytes, application/x-bzip2)
2008-02-22 16:33 EST, John Williams CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Williams CLA 2008-02-22 16:33:54 EST
Created attachment 90518 [details]
A project that demonstrates the problem.

Build ID: M20071023-1652

Steps To Reproduce:
Put the following interfaces in separate files in a new project.  Clean the project.  Hilarity ensues.

interface A extends Iterable<B> {}
interface B extends C {}
inteface C extends A {}

More information:
The compiler reports the following two errors:

Cycle detected: a cycle exists in the type hierarchy between B and C
The hierarchy of the type C is inconsistent

This problem is dependent on the order of compilation.  If the classes are renamed so that they compile in a different order, the problem disappears.
Comment 1 Kent Johnson CLA 2008-03-10 13:26:07 EDT
I've tried this case with a recent build and it works fine.


Please try this case on a more recent build to see if you still detect a problem.
Comment 2 Kent Johnson CLA 2008-03-13 12:51:23 EDT
Was able to reproduce in 3.3.2 but it works fine in the latest 3.4 build.

Closing as works for me.

Do not believe we'll be doing a 3.3.3 build.
Comment 3 Eric Jodet CLA 2008-03-26 03:05:01 EDT
Verified for 3.4M6 using build I20080324-1300: problem not reproduced