C语言中的面向对象编程实践与应用

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

《COOP C面向对象编程思想》是一本专注于介绍面向对象编程（Object-Oriented Programming, OOP）在C语言中的应用的教程。本书站在中立的角度，不偏袒任何编程范式，而是以ANSI-C为载体，深入探讨面向对象编程的核心概念和技术。首先，作者强调了没有任何一种编程技术能解决所有问题，也没有一种编程语言能保证始终产生正确结果。这表明编程是一个动态发展的领域，需要根据具体问题选择合适的工具和方法。然而，尽管如此，面向对象编程在当前被广泛认为是万能良药，因为它结合了长期以来我们所学习的良好编程原则，如模块化、封装和继承等。 C++、Eiffel、Oberon-2和Smalltalk等编程语言因其面向对象特性而被视为“新语言”，但这并不意味着非面向对象的C不能实现相同的功能。实际上，只要合理运用，即使在标准ANSI-C中，也能实现一定程度的代码重用。面向对象编程的关键优势在于它支持代码复用，使得开发者可以在不同项目之间共享组件，提高了开发效率。书中并非仅仅介绍如何使用C进行面向对象编程，而是着重于揭示其背后的思维模式和设计原则。例如，对象的概念，即把数据和操作数据的方法封装在一起，有助于组织代码并提高代码的可维护性。另外，继承机制允许创建具有共同特性的类，减少了重复代码，提升了代码的灵活性。此外，作者指出，虽然面向对象编程提倡从头开始开发每个项目，但好的程序员总是带着他们的工具箱和库，这与面向对象的复用理念相辅相成。在实践中，这意味着在理解和掌握基本原理后，开发者可以根据需要灵活地选择是否完全采用OOP风格，或者在C语言的框架下巧妙地融合面向对象和过程化的元素。《COOP 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页未读，继续阅读

wanqian122

粉丝: 0
资源: 7

C语言中的面向对象编程实践与应用

C面向对象编程

C语言实现面向对象思想编程

C语言的面向对象编程

Linux下C++面向对象编程指南与实用资源

coop:Projet Coop Vue.js

伟福COOP2000

coop-api

coop 游戏demo

bms-source-coop:黑色Mesa Source Coop容器

colab-coop-editor:CoLab Coop 3.0编辑器

最新资源