Thanks, you're right.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853735#3853735
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853735
---
This SF.Net email is s
Thanks!
I think you should include those few lines into the tutorial. It may help users.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853719#3853719
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853719
--
There still exits that bug. The compiler may produce a wrong call in
the following case:
class A {}
class B extends A {}
class C extends C {}
class X {
void foo(A a) { .. }
void foo(B b) { .. }
}
If you call foo(new C()) on an instance of X, the compiler may produce
a call to foo(A). B
Sorry the layout may be a little confussing... here is the right layout.
We can read this at the end of the tutorial :
anonymous wrote : The compiler does not correctly implement the Java method dispatch
algorithm. The compiler may confuse if methods defined in a class have the same name
but t