Bug 10500 - Shouldn't ignore inherited method with wrong argument types
Summary: Shouldn't ignore inherited method with wrong argument types
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.0 M4   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-28 12:05 EST by Philipe Mulet CLA
Modified: 2002-03-05 11:06 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2002-02-28 12:05:25 EST 
Build 20020226

We should reject the following code in 1.3 compliance mode (default):

class T {
      void foo(boolean b) {}
}

public class X {
      void foo(int i) {}
      void bar() {
            new T() {
                  {
                        foo(0); // should say that foo(boolean) isn't applicable
                  }
            };
      }
}
Comment 1 Philipe Mulet CLA 2002-02-28 12:15:30 EST 
Here is its friend scenario which we should also reject:

class T {
      void foo(boolean b) {}
}

public class X {
      void foo(int i) {}
      void bar() {
            new T() {
                  {
                        foo(false); // should complain ambiguity
                  }
            };
      }
}
Comment 2 Philipe Mulet CLA 2002-03-05 11:06:00 EST 
Tuned the #getImplicitMethod behavior to match 1.3 behavior.

Kent - please double check my fix candidate (released inside HEAD, post v_230).

Fixed