Nation Chirara

Stephan van Hulst wrote:The reason is because of the history of the Java language.

Static methods in interfaces were only added in Java 8. By that time, many classes were written that implement existing interfaces. When the developers allowed for static methods to be added to interfaces, they wanted to make sure that existing classes didn't suddenly break because the interface that they implemented had added a static method that happens to have the same name as a method in the class.

If interfaces had supported static methods from the very beginning, the first snippet of code probably would have caused a compilation error as well.

This drove the point home, I got you thanks!

Why does this compile? Am I not trying to override a static method here ?

interface A{ static void m1(){ System.out.println("A"); } } class B implements A{ public void m1(){} }

As this does not compile.

class A{ static void m1(){ System.out.println("A"); } } class B extends A{ public void m1(){} }

Thank you Ritchie for the informative answer, now I got it all.

Why would this fail to compile?

final double d=10; float f=d;

My thinking is that the compiler "must know" that 10 fits into float and d wont take another value because it is final.

where as this compiles?

final int d=10; byte f=d;