Java中抽象类和接口的区别.zip_javainterf资源-CSDN文库

共1个文件

doc：1个

版权申诉

12 浏览量 2022-09-21 22:02:02 上传评论收藏 18KB ZIP 举报

资源推荐

资源详情

资源评论

收起资源包目录

Java中抽象类和接口的区别.zip （1个子文件）

Java中抽象类和接口的区别.doc 62KB

Parsing Java Abstraction of the Difference Between Classes and

Interfaces

In Java language, abstract scale-up and with support class abstraction definition of

two mechanisms. Because of these two kinds of mechanism of existence, just gives Java

powerful object-oriented skills. Abstract scale-up and with between classes abstraction

definition for support has great similarities, even interchangeable, so many developers into

line non-abstract class definition for abstract scale-up and it is becoming more casual with

choice. In fact, both between still has the very big difference, for their choice even

reflected in problem domain essence of understanding, to design the intentions of the

understanding correctly and reasonable. This paper will for the difference analysis, trying

to give a developer with a choice between them are based.

Understand class abstraction

Abstract class and interface in Java language is used for abstract classes (in this article

non-abstract class not from abstract scale-up translation, it represents an abstract body, and

abstract scale-up for Java language used to define class abstraction in one way, please

readers distinguish) defined, then what are the abstract classes, use abstract classes for us

any good?

In object-oriented concept, we know all objects is through class to describe, but in

turn not such. Not all classes are used to describe object, if a class does not contain enough

information to portray a concrete object, this class is abstract classes. Abstract classes are

often used to characterization of problem field in our analysis, design that the abstract

concepts, is to the series will look different, but essentially the same exact conception of

abstraction. For example: if we carry out a graphical editing software development, will

find problem domain exists round, triangle so some specific concept, they are different, but

they all belong to shape such a concept, shape this concept in problem domain is not exist,

it is an abstract concept. Precisely because the abstract concepts in problem field no

corresponding specific concept, so to characterization abstract concepts non-abstract class

cannot be instantiated.

In an object-oriented field, mainly used for class abstraction types hidden. We can

construct a fixed a group of behavior of abstract description, but this group of behavior but

can have any a possible concrete implementation. This abstract describe is abstract classes,

and this an arbitrary a possible concrete realization is behaved for all possible derived class.

Modules can be operating an abstract body. Due to the module dependent on a fixed

abstraction body, so it can are not allowed to modify, Meanwhile, through the abstract

derived from the body, also can expand the behavior of this module function. Familiar with

OCP readers must know, object-oriented design to be able to achieve a core principle OCP

(Open - Closed flying), class abstraction is one of the key.

From the perspectives of grammar definition abstract class and interface

In grammatical perspective, Java language for abstract scale-up and with gives

different definitions below to define a way, called produce professional Demo abstract

class as an example to illustrate the difference.

In the abstract scale-up manner, produce professional Demo can have their own data

members, also can have the members of the abstract method, and with the realization of the

way, produce professional Demo can have only static cannot be modified data members,

all the members of the methods is abstract. In a sense, with a special kind of abstract class.

From programming, from the perspective of abstract scale-up and with can be used to

achieve "cancel" thoughts make themselves. But in the specific use top still have some

difference.

First, abstract class in Java language suggests is a kind of inheriting relationship, a

class can be used only once inheritance relationship (because Java do not support more

inheritance ZhuanZhu). - However, a class but can implement multiple with. Maybe it is

Java language designers in considering Java for multiple inheritance support of a

compromise to consider it.

Secondly, in the definition of abstract scale-up, we may give methods of default

behavior. But in with the definition of method cannot have the default behavior, to bypass

this limits, must use entrust, but it will add some complexity, sometimes can cause a lot of

trouble.

In class abstraction cannot define the default behavior is there another serious

problem that may cause on the maintenance of trouble. Because if later want to modify the

interface (usually by such abstract scale-up or with to represent) to adapt to the new

situation (e.g., adding new methods or to have already used the method to add new

parameters), will be very troublesome, might spend a lot of time (for a derived class many

situation, especially). But if the interface is through scale-up abstract to realize, then may

just need to modify defined in the abstract scale-up default behavior is ok.

Similarly, if not in abstract class defined in the default behavior, can lead to the same

method to appear in the abstract class every a derived class, violated "a-one rule," principle,

causing a-one place, the same code duplication against future maintenance. Therefore, in

the abstract scale-up and with a choice between should be careful.

From the design concept with abstract class and interface

It mainly from grammar definition and programming perspective, this paper discusses

the area with abstract class and don't, these levels difference is relatively low levels of, the

essence. This section will from another level: abstract class and with reflected design

concept, analyst the difference. The author thinks that from this level analysis to

understand the essence of both concepts.

As already mentioned, abstract class in Java language reveals a kind of inheriting

relationship, want to make reasonable, the inheritance relationship between parent class

and derived class must exist "is - a" relations, namely the super class and derived class in

concept in essence should be the same. For with criterion otherwise, it does not require

with of implementers and with defined in concept is essentially a consistent, only is

realized with defined a contract is just. In order to facilitate understandings.

Consider such a example, suppose in our problem field has a about filled the abstract

concepts, this filled with executive two movements open and close, then we can through

scale-up or abstract with to define a said the abstract concept of type, define each pattern .

Other concrete filled type can use extends the abstract class defined or filled with

defined using implements the filled. Look like using abstract class and with no much

difference.

If now requires more filled with alarm function. How can we design according to the

example of the class hierarchy? (in this case, it is mainly to show abstract class and with

reflected in the design ideas, distinction, other aspect problem unrelated all did simplified

or omitted)? Below will enumerate possible solutions, and from the design LiNianCeng

face these different schemes for analysis.

This method violated the object-oriented design of a core principles ISP (with flying

Segregation), in the definition of filled the filled concept itself inherent behavior methods

and another concept "alarm" behavior methods mix together. Such a problem is that those

who cause depends only upon the concept of modules will be held because "alarm" this

concept change (for example: modify the parameters) and alarm method, and vice still

change.

Since open and close and alarm belong to two different concepts, according to the ISP

principle should consider them separately defined in representatives of these two concepts

from the class abstraction. Definition means has: the two concepts are using abstract

scale-up defined; two concepts are used with defined; a concept using abstract scale-up

defined, another concept using with defined.

Obviously, due to Java language does not support multiple inheritance, so two

concepts are using abstract class defined is not feasible. The latter two ways are feasible,

but for their choice actually reflected in problem in the field of concept nature's

understanding, whether for design intent reflect the correct and reasonable. We are a result

analysis and description.

If the two concepts are used with ways to define, then reflects two problems: 1, we

may not understand clearly problem domain, AlarmDoor in concept essentially exactly is

held or alarm? 2, if we in problem field understanding no problems, for example: we

through for problem domain analysis found that AlarmDoor in concept in essence and

filled is consistent, then we realize when he failed to correct reveal our design intention,

because in these two concepts on the definitions (both use with defined) reflect reflected

these meanings.

If we in problem field understanding is: AlarmDoor in concept is essentially, at the same

time it is filled with alarm function. How should we come to the design, realization to clear

reflect what we mean by this? Front has said, in Java language abstract scale-up said in an

inheritance relationship, and inheriting relationship is in nature "is a" relationship. So for

评论收藏

内容反馈

版权申诉

JonSco

粉丝: 67
资源: 1万+

Java中抽象类和接口的区别.zip_java interf

最新资源

Java中抽象类和接口的区别.zip_java interf

Java中抽象类和接口的区别

Java的抽象类&接口的区别

Java抽象类与接口的区别

AMR_C_float_411.rar_3GPP_3GPP encoder.c_amr_interf_dec.c_语音编码

eetop.cn_DDR_PHY_Interface_Specification_v4_0.rar_DDR_PHY_Interf

amrlib.rar_AMR-wb_amr_amr-nb_codec source library_interf_enc.h

Using_srartdrive_software_commissioning_G120_inverter_by_means_of_PN_interf.pdf

java抽象类与接口的区别

java抽象类与接口区别

浅析Java抽象类与接口的区别.zip

java 抽象类与接口的区别介绍

Java 接口和抽象类区别

amr-wb 编码

jsr80 java 访问 usb

softap_ap6212a0_tinav2.1_验证通过_旧版本的系统_20170915_1223没有外层目录.7z

bpm:一个简单的基于Python的开源软件库，用于一维和二维线性或非线性时间相关的Schrödinger方程的数值模拟

Mex_C_Serial_Interf​ace:用于从 matlab 进行快速串行通信的 C_Serial 接口。-matlab开发

Java抽象类与接口区别详解

java 抽象类与接口的区别总结

java 中接口和抽象类的区别与对比

高级软件架构师培训讲义

捕鱼java源码-adapter:适配器

CDEGS 仿真教程 INTERF Chinese输电线路及管道线路之间的交流干扰分析.pdf

vue设置全局访问接口API地址操作

common_interfaces-release

最新资源

Mex_C_Serial_Interface:用于从 matlab 进行快速串行通信的 C_Serial 接口。-matlab开发