JVM Specification Reading 1

最新推荐文章于 2023-10-05 22:45:08 发布

bigmazhiyu

最新推荐文章于 2023-10-05 22:45:08 发布

阅读量729

点赞数

分类专栏： JVM 文章标签： Java

本文链接：https://blog.csdn.net/mshootingstar/article/details/44831065

版权

JVM 专栏收录该内容

3 篇文章 0 订阅

订阅专栏

今天读JVM Specification的introduce部分，读到这么一句：

JSR 335 also introduced private and static methods in interfaces at the class file level.

不可思议，接口中竟然可以定义方法了而且还可以定义静态方法！为什么要这么做？原来的abstract方法不是可以实现同样的功能么？为什么这么做？

有人在StackOverFlow（ http://programmers.stackexchange.com/questions/233053/why-were-default-and-static-methods-added-to-interfaces-in-java-8-when-we-alread ）上提出了反对观点：

In Java 8, interfaces can contain implemented methods, static methods, and the so-called "default" methods (which the implementing classes do not need to override).

In my (probably naive) view, there was no need to violate interfaces like this. Interfaces have always been a contract you must fulfill, and this is a very simple and pure concept. Now it is a mix of several things. In my opinion:

static methods do not belong to interfaces. They belong to utility classes.
"default" methods shouldn't have been allowed in interfaces at all. You could always use an abstract class for this purpose.

In short:

Before Java 8:

You could use abstract and regular classes to provide static and default methods. The role of interfaces is clear.
All the methods in an interface should be overriden by implementing classes.
You can't add a new method in an interface without modifying all the implementations, but this is actually a good thing.

After Java 8:

There's virtually no difference between an interface and an abstract class (other than multiple inheritance). In fact you can emulate a regular class with an interface.
When programming the implementations, programmers may forget to override the default methods.
There is a compilation error if a class tries to implement two or more interfaces having a default method with the same signature.
By adding a default method to an interface, every implementing class automatically inherits this behavior. Some of these classes might have not been designed with that new functionality in mind, and this can cause problems. For instance, if someone adds a new default method default void foo() to an interface Ix, then the class Cx implementing Ix and having a private foo method with the same signature does not compile.

What are the main reasons for such major changes, and what new benefits (if any) do they add?

主要意思是，他反对这种做法，认为静态方法应该属于静态类，而不应该属于接口，而default方法也不应该在接口中，应该在抽象类中。

原因是：1.接口中放了静态方法和default方法之后接口的概念不够清晰，而且接口和抽象类除了继承问题外没有太大区别。

2.原来只要定义在接口中的方法都要事先，现在有了default方法后，程序员可以不用重写，那么程序员很可能忘掉这点。

3.原来，你如果想要使用接口中的一个方法，你不得不实现所有的方法，这是一个优点，因为明确了所有的方法都要怎么实现，而现在如果一个类实现了两个接口，而这两个接口中有同名的default方法，那么直接编译异常（事实是编译器不知道该用哪个实现）。

4.那么为什么java不引进多重继承，而是在接口中定义default方法和静态方法呢？

针对这个问题，有各种解答：

有人的观点：

1静态方法的归属，静态方法是不优雅和惰性的，他应该被遗弃。当你使用很多的静态方法在程序中，单元测试和重构都会很麻烦。

2.多重继承是不好的，举例(the classic diamond problem)‌.

3.JAVA官方的例子：