当前位置：网站首页>Displays the difference between an implementation interface and an implicit implementation interface

Displays the difference between an implementation interface and an implicit implementation interface

2022-04-22 20:27:00 【InfoQ】

Difference between them ：

When implementing the interface implicitly , We have two ways to call methods that implement interfaces （GetName()）, namely ：

ICollect api=new Api();

api.GetName();

and

Api api=new Api();

api.GetName();

When explicitly implementing an interface , We have only one way to call GetName(), namely ：

ICollect api=new Api();

api.GetName();

? The final conclusion ：

1. When implementing the interface implicitly , Interfaces and classes （ The class that implements the interface ） Can access the methods in the class ;

2. When explicitly implementing an interface , Only the methods in the class can be accessed through the interface ;

Explicit benefits ：

Hide the implementation code of the class that implements the interface

Expanding knowledge ： In project development , Why write the interface first , Write the implementation class again ？

Defining interfaces and implementation classes respectively is the opening and closing principle in the architecture idea （ Extended development , Modify close ） The embodiment of , for example ：

If your registration is open to domestic users at the beginning , Successful registration of Chinese users returns “ Registered successfully ”, As the business expands , It needs to be open to overseas users , If the U.S. user returns “register success”, If you have an interface , Can be in the United States AmericaUserServiceImpl.java To achieve one UserService.java The interface of , To define the registration business of American users , Not in it UserServiceImpl
Android Open source project 《ali1024.coding.net/public/P7/Android/git》
.java add if else To handle different logic , such , Follow up if a
《Android Summary of learning notes + Latest mobile architecture video + Big Android interview questions + Project actual combat source code handout 》 Open source
There are changes in registered business in three regions , You only need to modify the implementation class of the corresponding region , The modification will not affect the implementation classes in other regions , Reduced coupling .

1、 The point of interface is abstract 、 not be punctilious , So that things of the same kind are universal and replaceable at the same height .

2、 In system analysis and Architecture , Distinguish between layers and dependencies , Each layer doesn't provide services directly to its upper layer （ That is, it is not directly instantiated in the upper layer ）, But by defining a set of interfaces , Only expose its interface function to the upper layer , The upper layer is only interface dependent to the lower layer , Instead of relying on concrete classes .?

What is the difference between an interface and an abstract class ？

Let's say C# Language as an example ,java It's the same thing .