What is the principle of opening and closing in Java

This article mainly explains "what is the principle of opening and closing in Java". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what is the principle of opening and closing in Java".

Definition: a software entity, such as classes, modules, and functions, should be open to extensions and closed to modifications

Build the framework with abstraction and extend the details with implementation

Advantages: improve software reusability and maintainability

Eg: go to work flexibly, must meet the 8-hour working hours, and let go to work when.

Core idea: facing abstract programming, in terms of verification, what to verify first, and then what to verify. It is open to add a new verification rule and cannot modify the history check to avoid affecting the history. Adopt abstraction, isolate and change later, abstract.

The image above:

Dashed line: represents implementation, and solid line represents inheritance.

There is a great risk of fundamental changes. -- > changes in the dao layer may have a great impact.

In object-oriented programming, the principle of opening and closing must be emphasized. Improve reusability and expansibility.

Thank you for your reading, the above is the content of "what is the principle of opening and closing in Java". After the study of this article, I believe you have a deeper understanding of what the principle of opening and closing in Java is, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!