Method resolution

[M Sharma]

PROGRAM 1
-------------------------

  
public class Test 
{
public void myMethod(String s) 
{ 
System.out.println("My String"); 
}
public void myMethod(StringBuffer sb) 
{ 
System.out.println("My StringBuffer"); 
} 
public static void main(String args[]) 
{ 
Test t = new Test(); 
t.myMethod(null); 
}
}
[B]The code does not compile. 
The compiler complains :
Test.java:16: reference to myMethod is ambiguous, both method myMethod(java.lang
.String) in Test and method myMethod(java.lang.StringBuffer) in Test match
                t.myMethod(null);
[/B]

Consider PROGRAM 2
---------------------------

public class Test 
{
public void myMethod(Object o) 
{ 
System.out.println("My Object"); 
}
 
public void myMethod(String s) 
{ 
System.out.println("My String"); 
}
public static void main(String args[]) 
{ 
Test t = new Test(); 
t.myMethod(null); 
}
}
[B]The code compiles cleanly and shows "My String"[/B]

Is this because that in case of PROGRAM 1, the classes String and StringBuffer are Peer - classes, therefore because of this it appears as a ambiguious call to compiler.
But in case of PROGRAM 2 where String and Object class references (where both are not peer classes) are used as the parameters in the methods, String being more specific is being selected and executed.
Well, i am not sure about the above reason, as its just a gut feeling. Pls guide me if i am wrong.

[Mika Leino]

I'd say your gut feeling is correct. Take a look at this thread here

[Mishra Anshu]

Yes..........I feel that's the reason.