C语言实现面向对象编程

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

"C语言实现面向对象的编程方法和原理探讨" 在C语言中实现面向对象的编程，虽然C本身并不支持直接的面向对象特性，但通过巧妙地利用C的结构体、指针和函数等机制，可以模拟实现封装、继承和多态这三大面向对象的核心特征。 1. 封装：在C语言中，我们可以创建结构体来模拟类的概念，将数据和操作数据的函数封装在一起。结构体内的成员变量可以视为类的属性，而函数则代表类的方法。通过设置访问权限（如只通过特定的接口函数访问结构体成员），可以实现数据的隐藏，达到封装的效果。 2. 继承：C语言不直接支持继承，但可以通过组合的方式实现类似的功能。一个结构体可以包含另一个结构体的实例作为其成员，这样就可以复用父结构体的属性和方法。同时，通过定义新的结构体和函数，可以扩展或覆盖父结构体的功能，实现继承的概念。 3. 多态：多态在C语言中通常通过函数指针实现。一个结构体可以包含指向函数的指针，这些函数可以有不同的实现，具体行为取决于结构体实例的类型。通过这种方式，同一个接口可以调用不同的函数，实现动态绑定，即多态性。在实际应用中，面向对象的C编程可能需要使用一些设计模式，比如工厂模式用于创建对象，单例模式确保类只有一个实例，策略模式允许在运行时选择算法等。通过这些模式，可以更好地在C语言中实现面向对象的设计思想。此外，C语言的面向对象实现往往涉及到一些复杂性，例如内存管理、类型安全以及性能优化等挑战。理解这些概念并熟练掌握其实践技巧，对于使用C语言进行面向对象编程至关重要。尽管C++提供了原生的面向对象支持，但理解如何在C中实现面向对象可以帮助我们深入理解面向对象的本质，并且在某些场景下，如嵌入式系统开发，使用C实现面向对象可能是更合适的选择。 C语言实现面向对象编程是一个挑战，但也是一种锻炼编程思维和技术深度的过程。通过封装、继承和多态的模拟实现，可以充分利用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页未读，继续阅读

kk1054497694

粉丝: 0
资源: 14

C语言实现面向对象编程

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

用c实现面向对象

用C实现面向对象，帮你理解面向对象

用C实现面向对象编程

用C实现面向对象.zip

用c实现面向对象 pdf格式

用c实现面向对象.rar

用c实现面向对象(oopc)

用C实现面向对象（英文版）

用C实现面向对象的技术 OO_techniques_in_C.pdf

最新资源