理解面向对象：用C语言实现OO编程

需积分: 50 13 浏览量更新于2024-07-29 收藏 1.2MB PDF 举报

"C语言实现面向对象编程的探索" 在编程世界中，没有一种技术能解决所有问题，也没有一种编程语言能确保程序始终无误。程序员也不应每次都从零开始构建项目。面向对象编程（OOP）是当前备受推崇的编程范式，尽管它已存在超过十年。其核心思想是将我们长期以来被教导的良好编程原则付诸实践。C++、Eiffel、Oberon-2和Smalltalk等语言因其支持面向对象特性而受到推崇，但即使不使用这些特性，使用像ANSI-C这样的纯C语言，也同样可以实现良好的代码复用。本书的目标不是吹捧面向对象编程或贬低传统的编程方式，而是利用ANSI-C来揭示面向对象编程是如何实施的，它包含哪些技术，以及这些技术如何帮助我们解决实际问题。面向对象的核心概念包括封装、继承和多态性，这些都是提升代码可读性、可维护性和可扩展性的关键。在C语言中实现面向对象，需要模拟这些特性。例如，封装可以通过结构体和指针实现，结构体用来存储数据，指针则作为访问结构体数据的方法，这样可以实现数据隐藏。继承则可以通过组合多个结构体或者使用宏定义来模拟，创建一个父类结构体并让子类结构体包含父类的实例。多态性则可以通过函数指针来实现，不同的对象可以有相同类型的函数指针，但执行不同的操作。 C语言中的面向对象编程可能不如C++那样直观和方便，但通过巧妙的设计和编码，可以达到类似的效果。例如，可以创建“类”的抽象，通过函数指针数组实现方法的动态绑定，从而实现类似于C++虚函数的功能。同时，使用工厂函数和类型标识符可以模拟类的构造和类型检查。在实践中，面向对象编程的复用性体现在类库的建立上。通过设计和实现一组相关的类，可以形成一套工具集，供不同项目重复使用。这不仅可以提高开发效率，还能降低错误率，因为经过验证的代码片段可以避免重复错误。用C语言实现面向对象编程需要对C语言的底层机制有深入理解，并且需要运用创新思维去模拟OOP的关键特性。这是一条挑战与收获并存的道路，对于理解C++和其他面向对象语言的工作原理大有裨益，也有助于提升开发者的设计和编程技能。

___________________________________________________________________________

1 Abstract Data Types

— Information Hiding

apply() calls action() for each element in set and passes the rest of the argument

list. action() must not change set but it may return zero to terminate apply() early.

apply() returns true if all elements were processed.

___________________________________________________________________________

Dynamic Linkage

Generic Functions

2.1 Constructors and Destructors

Let us implement a simple string data type which we will later include into a set.

For a new string we allocate a dynamic buffer to hold the text. When the string is

deleted, we will have to reclaim the buffer.

new() is responsible for creating an object and delete() must reclaim the

resources it owns. new() knows what kind of object it is creating, because it has

the description of the object as a first parameter. Based on the parameter, we

could use a chain of if statements to handle each creation individually. The draw-

back is that new() would explicitly contain code for each data type which we sup-

port.

delete(), however, has a bigger problem. It, too, must behave differently based

on the type of the object being deleted: for a string the text buffer must be freed;

for an object as used in chapter 1 only the object itself has to be reclaimed; and a

set may have acquired various chunks of memory to store references to its ele-

ments.

We could give delete() another parameter: either our type descriptor or the

function to do the cleaning up, but this approach is clumsy and error-prone. There

is a much more general and elegant way: each object must know how to destroy

its own resources. Part of each and every object will be a pointer with which we

can locate a clean-up function. We call such a function a destructor for the object.

Now new() has a problem. It is responsible for creating objects and returning

pointers that can be passed to delete(), i.e., new() must install the destructor infor-

mation in each object. The obvious approach is to make a pointer to the destructor

part of the type descriptor which is passed to new(). So far we need something like

the following declarations:

struct type {

size_t size; /* size of an object */

void (* dtor) (void *); /* destructor */

};

struct String {

char * text; /* dynamic string */

const void * destroy; /* locate destructor */

};

struct Set {

... information ...

const void * destroy; /* locate destructor */

};

___________________________________________________________________________

2 Dynamic Linkage — Generic Functions

It looks like we have another problem: somebody needs to copy the destructor

pointer dtor from the type description to destroy in the new object and the copy

may have to be placed into a different position in each class of objects.

Initialization is part of the job of

new() and different types require different work

— new() may even require different arguments for different types:

new(Set); /* make a set */

new(String, "text"); /* make a string */

For initialization we use another type-specific function which we will call a

construc-

tor. Since constructor and destructor are type-specific and do not change, we pass

both to new() as part of the type description.

Note that constructor and destructor are not responsible for acquiring and

releasing the memory for an object itself — this is the job of new() and delete().

The constructor is called by new() and is only responsible for initializing the memory

area allocated by new(). For a string, this does involve acquiring another piece of

memory to store the text, but the space for struct String itself is allocated by

new(). This space is later freed by delete(). First, however, delete() calls the des-

tructor which essentially reverses the initialization done by the constructor before

delete() recycles the memory area allocated by new().

2.2 Methods, Messages, Classes and Objects

delete() must be able to locate the destructor without knowing what type of object

it has been given. Therefore, revising the declarations shown in section 2.1, we

must insist that the pointer used to locate the destructor must be at the beginning

of all objects passed to delete(), no matter what type they have.

What should this pointer point to? If all we have is the address of an object,

this pointer gives us access to type-specific information for the object, such as its

destructor function. It seems likely that we will soon invent other type-specific

functions such as a function to display objects, or our comparison function differ(),

or a function clone() to create a complete copy of an object. Therefore we will use

a pointer to a table of function pointers.

Looking closely, we realize that this table must be part of the type description

passed to new(), and the obvious solution is to let an object point to the entire type

description:

struct Class {

size_t size;

void * (* ctor) (void * self, va_list * app);

void * (* dtor) (void * self);

void * (* clone) (const void * self);

int (* differ) (const void * self, const void * b);

};

struct String {

const void * class; /* must be first */

char * text;

};

___________________________________________________________________________

2.3 Selectors, Dynamic Linkage, and Polymorphisms

struct Set {

const void * class; /* must be first */

...

};

Each of our objects starts with a pointer to its own type description, and through

this type description we can locate type-specific information for the object:

.size is

the length that new() allocates for the object; .ctor points to the constructor called

by new() which receives the allocated area and the rest of the argument list passed

to new() originally; .dtor points to the destructor called by delete() which receives

the object to be destroyed; .clone points to a copy function which receives the

object to be copied; and .differ points to a function which compares its object to

something else.

Looking down this list, we notice that every function works for the object

through which it will be selected. Only the constructor may have to cope with a

partially initialized memory area. We call these functions methods for the objects.

Calling a method is termed a message and we have marked the receiving object of

the message with the parameter name self. Since we are using plain C functions,

self need not be the first parameter.

Many objects will share the same type descriptor, i.e., they need the same

amount of memory and the same methods can be applied to them. We call all

objects with the same type descriptor a class; a single object is called an instance

of the class. So far a class, an abstract data type, and a set of possible values

together with operations, i.e., a data type, are pretty much the same.

An object is an instance of a class, i.e., it has a state represented by the

memory allocated by new() and the state is manipulated with the methods of its

class. Conventionally speaking, an object is a value of a particular data type.

2.3 Selectors, Dynamic Linkage, and Polymorphisms

Who does the messaging? The constructor is called by new() for a new memory

area which is mostly uninitialized:

void * new (const void * _class, ...)

{ const struct Class * class = _class;

void * p = calloc(1, class —> size);

assert(p);

* (const struct Class **) p = class;

if (class —> ctor)

{ va_list ap;

va_start(ap, _class);

p = class —> ctor(p, & ap);

va_end(ap);

}

return p;

}

The existence of the struct Class pointer at the beginning of an object is extremely

important. This is why we initialize this pointer already in new():

___________________________________________________________________________

2 Dynamic Linkage

— Generic Functions

•p

object

•

...........

class

size

ctor

dtor

clone

differ

struct Class

The type description class at the right is initialized at compile time. The object is

created at run time and the dashed pointers are then inserted. In the assignment

* (const struct Class **) p = class;

p points to the beginning of the new memory area for the object. We force a

conversion of p which treats the beginning of the object as a pointer to a struct

Class and set the argument class as the value of this pointer.

Next, if a constructor is part of the type description, we call it and return its

result as the result of new(), i.e., as the new object. Section 2.6 illustrates that a

clever constructor can, therefore, decide on its own memory management.

Note that only explicitly visible functions like new() can have a variable parame-

ter list. The list is accessed with a va_list variable ap which is initialized using the

macro va_start() from stdarg.h. new() can only pass the entire list to the construc-

tor; therefore, .ctor is declared with a va_list parameter and not with its own vari-

able parameter list. Since we might later want to share the original parameters

among several functions, we pass the address of ap to the constructor — when it

returns, ap will point to the first argument not consumed by the constructor.

delete() assumes that each object, i.e., each non-null pointer, points to a type

description. This is used to call the destructor if any exists. Here, self plays the

role of p in the previous picture. We force the conversion using a local variable cp

and very carefully thread our way from self to its description:

void delete (void * self)

{ const struct Class ** cp = self;

if (self && * cp && (* cp) —> dtor)

self = (* cp) —> dtor(self);

free(self);

}

The destructor, too, gets a chance to substitute its own pointer to be passed to

free() by delete(). If the constructor decides to cheat, the destructor thus has a

chance to correct things, see section 2.6. If an object does not want to be deleted,

its destructor would return a null pointer.

All other methods stored in the type description are called in a similar fashion.

In each case we have a single receiving object self and we need to route the

method call through its descriptor:

剩余220页未读，继续阅读

yuankangjian_1

粉丝: 0
资源: 1

理解面向对象：用C语言实现OO编程

用C语言实现面向对象编程.pdf

用C语言实现面向对象编程

用C语言实现面向对象研究.pdf

用c语言实现面向对象

使用C语言实现面向对象编程

使用C语言实现面向对象编程实践指南

使用C语言实现面向对象的嵌入式软件开发

请用c语言实现面向对象

一款高效的Vue 3低代码表单，可视化设计，一键生成源码

Python第八周作业

最新资源