Unix编程艺术：设计与实现的深度探索

5星 · 超过95%的资源需积分: 0 31 浏览量更新于2024-07-24 收藏 3.78MB PDF 举报

"Unix编程艺术英文版" 是一本由Eric S. Raymond撰写的书籍，深入探讨了Unix系统的设计哲学、开发原则以及实践经验。这本书包含了Unix领域的专家们的专业见解，涵盖了Unix社群文化、软件开发设计与实现等多个方面，展现了作者在Unix领域的深厚经验和独特洞察。在"Unix编程艺术"中，Eric S. Raymond (ESR)揭示了Unix系统背后的设计原则，这些原则包括简洁性、模块化、工具间的协同工作以及对文本流的重视。他强调了使用shell脚本和管道来组合简单命令以完成复杂任务的高效方法。书中还讨论了Unix如何通过可重用的库和接口鼓励代码复用，以及如何通过版本控制系统促进协作开发。书中涵盖的内容广泛，从早期Unix的历史到现代Unix系统的演变，ESR详尽地阐述了Unix开发者的思考方式和工作方式。他还探讨了Unix的开放源码文化，解释了开源运动对软件开发的影响，以及如何通过开放的社区合作来改进和扩展软件。在技术层面上，书中的章节可能涉及以下主题： 1. Unix哲学：讲解如何遵循Unix设计原则进行程序开发，例如“每个程序做一件事并且做好”。 2. 命令行界面：介绍如何有效使用shell和命令行工具，如grep、sed和awk等。 3. 文本处理：讨论Unix对文本流的处理方式，以及如何通过管道和重定向来构建复杂的流程。 4. I/O系统：涵盖了fcntl和ioctl等Unix系统调用，以及它们在错误处理和设备控制中的应用。 5. 文件系统：分析Unix的文件系统结构，包括文件权限、硬链接和符号链接。 6. 网络编程：讲解Unix下的网络通信，包括套接字编程和网络协议的实现。 7. 程序设计：讨论C语言在Unix中的作用，以及异常处理和C++的相关话题。 8. 错误处理：如何在Unix环境中优雅地处理错误和异常情况。 9. 工具和库：介绍Unix开发中常用的工具和库，如Makefile的编写和库的使用。 10. 版本控制：探讨版本控制系统如Git在Unix开发中的重要性。这本书不仅适合经验丰富的Unix开发者，也适合想要了解Unix系统工作原理和设计思想的初学者。通过阅读，读者能够理解为何Unix系统在软件工程领域中占据重要地位，并学习到如何更有效地在Unix环境下进行编程和系统设计。《Unix编程艺术》是一本深入探讨Unix精髓的著作，它不仅仅关于编程，更是关于一种高效、优雅的解决问题的思维方式和文化。

Preface

Table of Contents

Who Should Read This Book

How To Use This Book

Related References

Conventions Used In This Book

Our Case Studies

Author's Acknowledgements

Unix is not so much an operating system as an oral history.

--Neal Stephenson

There is a vast difference between knowledge and expertise. Knowledge lets you deduce the

right thing to do; expertise makes the right thing a reflex, hardly requiring conscious thought

at all.

This book has a lot of knowledge in it, but it is mainly about expertise. It is going to try to

teach you the things about Unix development that Unix experts know, but aren't aware that

they know. It is therefore less about technicalia and more about shared culture than most

Unix books — both explicit and implicit culture, both conscious and unconscious traditions.

It is not a “how-to” book, it is a “why-to” book.

The why-to has great practical importance, because far too much software is poorly

designed. Much of it suffers from bloat, is exceedingly hard to maintain, and is too difficult

to port to new platforms or extend in ways the original programmers didn't anticipate. These

problems are symptoms of bad design. We hope that readers of this book will learn

something of what Unix has to teach about good design.

This book is divided into four parts: Context, Design, Tools, and Community. The first part

(Context) is philosophy and history, intended to provide foundation and motivation for what

follows. The second part (Design) unfolds the principles of the Unix philosophy into more

specific advice about design and programming. The third part (Tools) focuses on the

software Unix provides for helping you solve problems. The fourth part (Community) is

about the human-to-human transactions and agreements that make the Unix culture so

effective at what it does.

Because this is a book about shared culture, the author never planned to write it alone. You

will notice that the text includes guest appearances by prominent Unix developers, the

shapers of the Unix tradition. The book went through an extended public review process

during which the author invited these luminaries to comment on and argue with the text.

Rather than submerging the results of that review process in the final version, these guests

were encouraged to speak with their own voices, amplifying and developing and even

disagreeing with the main line of the text.

This book is written using the editorial ‘we’ not to pretend omniscience but reflecting the

fact that it is an attempt to articulate the expertise of an entire community. One of the

‘guests’ will be the author himself, occasionally speaking in first person to convey a

reminiscence, a war story, or a personal opinion that is not necessarily reflective of the Unix

community at large.

Because this book is aimed at transmitting culture, it includes much more in the way of

history and folklore and asides than is normal for a technical book. Enjoy; these things, too,

are part of your education as a Unix programmer. No single one of the historical details is

vital, but the gestalt of them all is important. We think it makes a more interesting story this

way. More importantly, understanding where Unix came from and how it got the way it is

will help you develop an intuitive feel for the Unix style.

For the same reason, we refuse to write as if history is over. You will find an unusually large

number of references to the time of writing in this book. We do not wish to pretend that

current practice reflects some sort of timeless and perfectly logical outcome of preordained

destiny. References to time of writing are meant as an alert to the reader two or three or five

years hence that the associated statements of fact may have become dated and should be

double-checked.

Other things this book is not is neither a C tutorial, nor a guide to the Unix commands and

API. It is not a reference for sed or Yacc or Perl or Python. It's not a network programming

primer, nor an exhaustive guide to the mysteries of X. It's not a tour of Unix's internals and

architecture, either. There are other books that cover these specifics better, and this book will

point you at them as appropriate.

How To Use This Book

Preface

How To Use This Book

This book is both practical and philosophical. Some parts will be aphoristic and general,

others will examine specific case studies in Unix development. We will try to precede or

follow general principles and aphorisms with examples that illustrate them; examples drawn

not from toy demonstration programs but rather from real working code that is in use every

day.

We have deliberately avoided filling the book with lots of code or specification-file

examples, even though in many places this might have made it easier to write (and in some

places perhaps easier to read!). Most books about programming give too many low-level

details and examples, but fail at giving the reader a high-level feel for what is really going

on. In this book, we prefer to err in the opposite direction.

Therefore, while you will often be invited to read code and specification files, relatively few

are actually included in the book. Instead, we'll point you at examples on the Web.

All the code referenced in this book is available on-line, in open source, over the Internet.

Use that resource! The case studies we choose are exemplars. You'll notice that some of

these exemplars come up repeatedly, as case studies from different angles. This is deliberate;

it is intended to reduce the amount of code and documentation you have to read in order to

observe the entire range of design patterns we discuss.

Absorbing these examples will help solidify the principles you learn into semi-instinctive

working knowledge. Ideally, you should read this book near the console of a running Linux

system, with a web browser handy. Any Unix will do, but the software case studies are more

likely to be immediately available for inspection on a Linux box. The pointers in the book

are invitations to browse and experiment. Introduction of these pointers is paced so that

wandering off to explore for a while won't break up exposition that has to be continuous.

Note: while we have made every effort to cite URLs that should remain stable and usable,

there is no way we can guarantee this. If you find that a cited link has gone stale, use

common sense and do a phrase search with your favorite Web search engine. Where possible

we suggest ways to do this near the URLs we cite.

剩余510页未读，继续阅读

wz3118103

粉丝: 27
资源: 11

Unix编程艺术：设计与实现的深度探索

UNIX 编程艺术(中文版)

UNIX编程艺术.pdf

Unix编程艺术/Unix环境高级编程（第二版）/Unix网络编程（第二版）

Unix编程艺术英文版

unix编程艺术 英文版

UNIX编程艺术英文版PDF：程序员必读经典

UNIX编程艺术英文版：自由与商业授权详解

unix编程艺术英文

unix 编程艺术（英文版）

英文版 unix编程艺术

最新资源

unix编程艺术英文版