Enthuware

Interesting question, seems basic but I answered wrong! (AFTER having passed the 1Z0-803 exam with 98%...)

In the solution it is stated: But in practical use I would suggest the following (clearer, but both versions work):
[/b]

Yes, if you use T1.VALUE, there is no ambiguity. The ambiguity arises when you try to use tc.VALUE. The given solution illustrates how to disambiguate the member that you want to use.

HTH,
Paul.

Hi
I would like to know wether I can define a non final static fields in an interface.

EDIT: all fields in an interface are implicitly static and final.

That is correct. You cannot have non-final static fields in an interface. All fields are implicitly public, static, and final even if you don't declare them so.
-Paul.

VALUE is not used in TestClass. So unless VALUE is used, there should be nothing wrong in the code. So, second option "There is nothing wrong with the code" can also be correct.
Let me know your comments.

"There is nothing wrong with the code" is indeed the correct answer.

How will TestClass know which m1() to implement?

It seems like it would create a compile-time error which is why I thought D was the correct answer.

Even though m1 is declared in two interfaces, their signatures are same. So both the interfaces are satisfied with the same implementation.

I respect the Java Overlords, but talk about ambiguous test questions.
The question asks what is wrong with the code.
Answer is - nothing wrong with the code.
Explanation - technically something wrong with the code.
It's not like this is good practice to write code like this either. ZOMG. RIP. #SADBOYZ

admin wrote:Even though m1 is declared in two interfaces, their signatures are same. So both the interfaces are satisfied with the same implementation.

So, its ok to declare two methods with exactly the same signatures (with exact same params as well)?

And is it just in two interfaces or could we do this in two different classes(subclasses) as well? And can we call this an override?

Yes, in the given situation, it is ok. In other situations, such as in the same class or same interface, it is not ok. In a class/subclass, it is called overriding. You need to try it out.

Thank you. Yes. I will.