Method Signature Not Enforced ?

Question

Good day to the forum. This is an odball to me. Please tell me what's wrong with this picture.....
public void foo(double d)
public void bar()
  int i = 100;
  foo(i);
}Why is JBuilder and my compiler allowing this?

Answer 1

jverd
as long as you use objects and not primitives you can
be sure as to which method would be called - am i
correct. for my own information.
public class DataValue {
void  set(Integer i) {}
void set(Double d) {}
void ... main() {
DataValue dv = new DataValue();
dv.set( new Integer(10) );
dv.set(new Double(20.25);
What if you have a method that takes Number, and you pass it a Long? Or a Float? That kind of thing can lead to similar confusion.
But actually, if you read and understand the JLS, then you can always be sure which method will be called. It's never ambiguous which method will be called. Often confusing though: void foo(String s, Object o) {}
void foo(Object o, String s) {}
void foo(Object o1, Object o1) {}
foo ("x", "y"); I don't know which one will get called. It may even be a compiler error. But I would know if I dug around in the spec enough.