Bug 75548 - [1.5] Compiler behavior differs from Sun's re: finding constructors in generic parent classes (example attached)
Summary: [1.5] Compiler behavior differs from Sun's re: finding constructors in generi...
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: 3.1 M3   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-03 16:55 EDT by Cliff Biffle CLA
Modified: 2004-10-25 09:36 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cliff Biffle CLA 2004-10-03 16:55:00 EDT
The Eclipse IDE marks as errant a situation that isn't, in the opinion of javac from 1.5.  I realize that 1.5 
support in Eclipse is new (I'm running 3.1M2), so I assume nobody else has run into this esoteric 
situation.

Here's the situation:

class Cache<K, V> {
}

class Index<K, V> {
  public Index(Cache<?, V> parentCache) {
  }
}

class MyCache extends Cache<Integer, String> {
  class AnIndex extends Index<String, String> {
    public AnIndex() {
      super(MyCache.this); // <-- Eclipse cannot find the constructor!
    }
  }
}

This is a simplified test case for the problem; we encountered it in one of our production systems.  
javac from Sun's 1.5 distribution does not consider this an error, but Eclipse does.

Thanks!
Comment 1 Philipe Mulet CLA 2004-10-25 09:17:07 EDT
Cannot reproduce any longer with HEAD's content
Comment 2 Philipe Mulet CLA 2004-10-25 09:35:04 EDT
Got addressed indirectly since 3.1M2.
Comment 3 Philipe Mulet CLA 2004-10-25 09:36:23 EDT
likely dup of bug 73963