The file name is A.java
class A
{
publicfinalstaticvoid main(String args[])
{
System.out.println("in A");
A a =new B();
a.main(args);
}
}
class Bextends A
{
publicstaticvoid main(String args[])
{
System.out.println("in B");
}
}
i expect output to be
in A
in B
but I get stuck in a loop, that prints in A continously
oops!, final modifier was just an experiment, it shudnt be there, assume that it is not there
anyways, i understood that static methods cannot be overriden
I wonder how it allows me to compile, when in C++ i get an error if i use virtual and static at the same time
Message was edited by:
enterneo
Message was edited by:
enterneo
> I would have expected a warning at least.
uh, no.
It is quite acceptable (technically) to hide a static method behind another static method.
It's bad form, generally frowned upon, but there's no reason it shouldn't be technically possible (and there may in fact sometimes be a semi-legitimate purpose behind it, though in such cases the method usually shouldn't have been static to begin with).
> and there may in fact sometimes be a semi-legitimate purpose behind it,
> though in such cases the method usually shouldn't have been static to begin with
I thought the reason was for this case:
//today:
class A {}
class B extends A {
public static void f() {}
}
//tomorrow:
class A {
public static void f() {}
}
class B extends A {
public static void f() {}
}
It was considered desirable that adding f to A doesn't break B.
Imagine A is a class in some library and B is a client-written class.
> Because in Java you can't use virtual and
> static at the same time, because virtual isn't part
> of the language,
Well, not explicitly. Every non-private, non-final, non-static method is virtual--or at least polymorphs in the way virtual specifies in C++. But then, that may be a bit of a stretch to begin with, since, as I hope the OP unerstands now, Java != C++.
