public interface I1
{
public void work();
}

public interface I2
{
String name = “I2 name”;
public void work();
}

public class MultipInhe implements I1, I2
{

@Override
public void work()
{
// TODO Auto-generated method stub

}

public static void main(String[] args) {
System.out.println(name);
}

}

From which interface, work () method is interesting?

What problems do you get once specifications and tests enter the field? Does the candidate understand the semantics of subtyping/inheritance (in general and in Java)?

My interest has swayed from proxy based AOP stuff towards compile-time code introduction such as what the Project Lombok guys are doing.

@Stephan – Qi4J looks really interesting – quite a different way to approach things! Have you built anything with it?

So there is no ‘interface inheritance’ – that’s implementation.

Java has multiple implementation / single inheritance.

First because the question you are asking is vague: what kind of inheritance are you talking about, implementation or interface?

Java doesn’t emulate anything: it supports multiple inheritance of interfaces and it doesn’t support multiple inheritance of implementation. C++ supports both.