Bug 10500

Summary:	Shouldn't ignore inherited method with wrong argument types
Product:	[Eclipse Project] JDT	Reporter:	Philipe Mulet <philippe_mulet>
Component:	Core	Assignee:	Kent Johnson <kent_johnson>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P2
Version:	2.0
Target Milestone:	2.0 M4
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Philipe Mulet

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

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

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