C标准库英文版详解：ANSI/ISO标准函数与跨平台代码示例

需积分: 13 38 浏览量更新于2024-07-28 收藏 24.99MB PDF 举报

"C标准库英文版"文档是一份详尽的资源，它深入解析了C语言标准库的各个方面。这份文档的核心内容围绕着一系列标准库头文件，包括但不限于<stdio.h>、<stdlib.h>、<math.h>、<string.h>、<setjmp.h>、<signal.h>、<time.h>、<limits.h>、<float.h>、<stdbool.h>、<stdarg.h>、<time.h>、<ctype.h>和<cstring.h>。这些库文件是C语言编程的基础，它们提供了丰富的功能，如输入输出操作、数学函数、字符串处理、错误处理、类型定义、信号处理、时间管理、字符分类等。文档强调了这些标准库在ANSI和ISO标准中的地位，确保了代码的跨平台兼容性。作者通过展示大约9,000行经过测试且可运行的代码示例，帮助读者理解如何在实际编程中有效利用这些库函数。特别关注的是，书中还探讨了C标准中新增的功能，如多locale支持（即对不同文化习俗的适应）和大型字符集（如日文字符），这些都是现代C编程中不可或缺的部分。此外，"C标准库英文版"不仅解释了库的使用方法，还指导开发者如何正确地设计和实现库的使用，确保程序的稳定性和效率。书中的代码实例都经过了严格的测试，读者可以通过学习和实践这些例子，提升自己的C语言编程技能，并了解如何在实际项目中灵活运用标准库。这本文档是C程序员必备的参考书籍，无论你是初学者还是经验丰富的开发人员，都能从中收获关于C标准库的深入理解和实践经验。通过阅读和掌握这些内容，你将能够更好地编写出高效、可移植的C程序。

Preface

Good books have been written on how to write mathematical functions.

Other books present specialized libraries for a variety of purposes. They

show you how to use the library presented. Some may even justify many

of the design choices for the particular library in question.

FaY,

if any,

endeavor to teach the skills required for library building in general.

reusability

number of books present general principles for designing and imple

menting software. The disciplines they present have names such as struc

tured analysis, structured design, object

oriented design, and structured

programming. Most examples in these books consider only programs

written for a custom application. Nevertheless, the principles and disci

plines apply equally well to the writing of reusable libraries.

The goal of reusability simply raises the stakes.

If a library function is

not highly cohesive, in the structured

design sense, then it is less likely to

find new uses. If it does not have low coupling, in the same sense, it is

harder to use. Similarly, a collection of functions must hide implementation

details and provide complete functionality. Otherwise, they fail at

irnple-

menting reusable data abstractions, in the object

oriented sense.

So the final purpose of this book is to address the design and implemen

tation issues peculiar to library building. The design of the Standard

library is fixed. Nevertheless, it is a good design in many ways and worthy

of discussion. Implementations of the Standard

library can vary. Any

number of choices are strongly dictated by general principles, such

correctness and maintainability. Other choices are dictated by priorities

peculiar to a project, such as very high performance, portability or small

size. These choices and principles are also worthy of discussion.

structure

The book is structured much like the Standard

library itself. Fifteen

this

headers declare or define all the names in the library. A separate chapter

book

covers each header. Most of the headers have reasonably cohesive contents.

That makes for reasonably cohesive discussions. One or two, however, are

catchalls. Their corresponding chapters are perforce wider ranging.

I include in each chapter excerpts from relevant portions of the

IS0

Standard. (Aside from formatting details, the IS0 and ANSI

Standards,

are identical.) The excerpts supplement the narrative description of how

each portion of the library is customarily used. They also help make this

book a more complete reference (that is nevertheless more readable than

the

Standard alone). I also show all code needed to implement that

portion and

test the implementation.

Each chapter ends with references and a set of exercises. In a university

course based on this book, the exercises can serve

homework problems.

Many of them are simple exercises in code rewriting. They

drive home a

point or illustrate reasonable variations in implementation. The more

ambitious exercises are labelled as such. They can serve as a basis for more

extended projects. The independent reader can simply use the exercises as

an impetus for further thought.

bbs.theithome.com

xii

Preface

The

Code

The code presented in this book has been tested with

compilers from

Borland, Project GNU, and

VAX ULTRIX. It has passed the widely used

Plum Hall Validation Suite tests for library functions. It has also survived

an assortment of public

domain programs designed to stress

implemen

tations and illuminate their darker corners. While I have taken pains to

minimize errors, I cannot guarantee that none remain. Please note the

disclaimer on the copyright page.

Please note also that the code in this book is protected by copyright. It

has

not

been placed

the public domain. Nor is it shareware. It is not

protected by a

"mpyleft" agreement, like code distributed by the Free

Software Foundation (Project GNU). I retain all rights.

fair

use

You are welcome to transcribe the code to machine

readable form for

your personal use. You can purchase the code in machine

readable from

The C Users Group in Lawrence, Kansas. In either case, what you do with

the code is limited by the

fair use

provisions of copyright law. Fair use

does

not

permit you to distribute copies of the code, either hard copy or

machine

readable, either free or for a fee.

Having said that, I do permit one important usage that goes well beyond

fair use. You can compile portions of the library and link the resultant

binary object modules with your own code to form an executable file. I

hereby permit you to distribute unlimited copies of such an executable file.

ask no royalty on any such copies. I do, however, require that you

document the presence of the library, whatever amount you use, either

modified or unmodified. Please include somewhere in the executable file

the following sequence of characters:

miom

this

are

derived

frnm

'Ihe

Standard

Lihary,

-@-it

(c)

1992

P.J. P-,

published

Prentice-Hall,

ard

are

ueed

with

pnnissirn.

The same

message should appear prominently, and in an appropriate place, on any

documentation that you distribute with the executable image. If you omit

either message, you infringe the copyright.

licensing

You can also obtain permission to do more. You can distribute the entire

library in the form of binary object modules. You can even distribute copies

of the source files from this book, either modified or unmodified. You can,

in short, incorporate the library into a product that lets people use it to make

executable programs. To do so, however, requires a license. You pay a fee

for the license. Contact Plum Hall Inc. in Kamuela, Hawaii for licensing

terms and for on

going support of the library.

Despite the mercenary tone of these paragraphs, my primary goal is not

to flog a commercial product.

believe strongly in the

Standard, having

worked very hard to help bring it about. Much of my effort went into

developing the specification for the Standard

library. I want to prove that

we have constructed a good language standard. I wrote this implementa

tion, and this book, to demonstrate that simple but important fact.

bbs.theithome.com

Preface

xiii

Acknowledgments

Compass, Inc. of Wakefield, Massachusetts believed in this project long

before it was completed. They are my first customer for the library code.

They helped test, debug, and improve the library extensively in the process

of accepting it for use with their Intel

860

compiler. Ian Wells, in particular,

bore the brunt of my delays and botches with good

natured professional

ism. Don Anderson contributed many a midnight e

mail message toward

making this library hang together properly. For their faith and patience,

heartily thank everyone I have worked with at Compass.

Paul Becker, my Publisher at Prentice

Hall, also believed in this project.

His gentle but persistent goading was instrumental in bringing this book

to completion. The (anonymous) reviewers he employed helped me

sharpen my focus and tone down some of the more extreme prose. Paul's

professionalism reminded me why Prentice

Hall has been such a major

force in technical publishing for so long.

Moving to Australia for a year part way through this project presented

a bouquet of impediments. My good friend and business colleague John

O'Brien of Whitesmiths, Australia, was always there to help. For turning

thorns into roses, he has been nonpareil. His assistance has surpassed the

bounds even of friendship.

Andrew Binnie, Publishing Manager at Prentice Hall Australia

kindly

provided the laser printer I needed to finish this book. He was quick to help

in many ways. The University of New South Wales Computer Science

Department graciously gave me the time and space I needed, even though

they had other plans for both.

Tom Plum has forced many of us to think deeply about fundamental

aspects of C. I have enjoyed numerous fruitful discussions with him on the

topics covered here. Dave Prosser has also freely shared his deep insights

into the workings of C. As editor of both the ANSI and

IS0 C Standards,

Dave provided the machine

readable text excerpted extensively in this

book. Advanced Data Controls Corp. of Tokyo, Japan pioneered Kanji

support in C.

Takashi Kawahara and Hiroshi Fukutomi, both principals in

that company, have been very helpful in educating me on the technical

needs of Japanese programmers.

Much of the material presented here first appeared in monthly install

ments in

The

Users

Journal.

Robert Ward has been a particularly easy

publisher to work with.

appreciate his flexibility in letting me recycle

material from his magazine. Jim Brodie has been equally generous in

permitting me to use material from our book

Standard

Reading technical manuscripts is never an easy task. Both John O'Brien

and Tom Plum reviewed portions of this book and provided helpful feed

back. Those who caught (some of the numerous) errors in the first printing

include Nelson H.F.

Beebe, Peter Chubb, Stephen D. Clamage, Steven

Pemberton, Tom Plum, and Ian

LanceTaylor.

bbs.theithome.com

Chapter

Introduction

Background

libra

is a collection of program components that can be reused in

many programs. Most programming languages include some form of

library. The programming language

is no exception. It began accreting

useful

functions

right from the start. These functions help you classify

characters, manipulate character strings, read input, and write output

to name just a few categories of services.

few

You must

declare

a typical function before you use it in a program. The

definitions

easiest way to do so is to incorporate into the program a

header

that declares

all the library functions in a given category.

header can also define any

associated

type definitions

and

macros.

A header is as much a part of the

library

the functions themselves. Most often, a header is a

text file

just

like the you write to make a program.

You use the

#include

directive in a

source file to make a header part

of the

translation unit.

For example, the header

<stdio.

declares functions

that perform input and output. A program that prints a simple message

with the function

printf

consists of the single

source file:

a simple test program

#include <stdio

int main (void)

{

say hello

printf

(

"Hello\n"

)

;

return

(0);

translator

converts each translation unit to an

object module,

a form

suitable for use with a given

computer architecture

(or

machine).

linker

combines all the object modules that make up a program. It incorporates

any object modules you use from the

library

well. The most popular

form of translator is a

compilw.

It produces an

executable file.

Ideally at least,

an executable file contains only those object modules from the library that

contain functions actually used by the program. That way, the program

suffers no size penalty as the

library grows more extensive. (Another

form of translator is an

interpreter.

It may include the entire

library as part

of the program that interprets your program.)

bbs.theithome.com

剩余516页未读，继续阅读

feng06358

粉丝: 5
资源: 4

C标准库英文版详解：ANSI/ISO标准函数与跨平台代码示例

C语言标准库详解（英文版）

C语言标准库权威指南

C语言标准库详解及实现

C标准库英文版.pdf

C标准库-中文.rar_C 标准库_C语言标准_c语言标准库_中文_语言库

c语言标准库

C语言标准库

C语言标准库源码

C语言标准库详解

c语言 标准库 所有

最新资源

c语言标准库所有