java中interface之间嵌套,为什么在Java中使用静态嵌套接口？

I have just found a static nested interface in our code-base.

class Foo {

public static interface Bar {

/* snip */

}

/* snip */

}

I have never seen this before. The original developer is out of reach. Therefore I have to ask SO:

What are the semantics behind a static interface? What would change, if I remove the static? Why would anyone do this?

解决方案

The static keyword in the above example is redundant (a nested interface is automatically "static") and can be removed with no effect on semantics; I would recommend it be removed. The same goes for "public" on interface methods and "public final" on interface fields - the modifiers are redundant and just add clutter to the source code.

Either way, the developer is simply declaring an interface named Foo.Bar. There is no further association with the enclosing class, except that code which cannot access Foo will not be able to access Foo.Bar either. (From source code - bytecode or reflection can access Foo.Bar even if Foo is package-private!)

It is acceptable style to create a nested interface this way if you expect it to be used only from the outer class, so that you do not create a new top-level name. For example:

public class Foo {

public interface Bar {

void callback();

}

public static void registerCallback(Bar bar) {...}

}

// ...elsewhere...

Foo.registerCallback(new Foo.Bar() {

public void callback() {...}

});