Unix编程艺术：经典指南

需积分: 12 19 浏览量更新于2023-06-13 收藏 3.78MB PDF 举报

"《Unix编程艺术》(The Art of Unix Programming)是一本由Eric Steven Raymond所著的专业书籍，它深入探讨了Unix系统的精髓和设计哲学，旨在向读者传授Unix编程的核心技巧和最佳实践。这本书的创作历程始于1999年，经过多次修订，从最初的四章公共HTML草案，到2003年1月的十八章节初稿，作者在每版中都进行了详尽的审阅和改进，以确保内容的准确性和深度。《Unix编程艺术》涵盖了广泛的主题，包括但不限于：Unix系统的底层原理、命令行接口（CLI）的高效利用、文件系统的设计思想、网络编程、进程管理、shell脚本、以及与C语言和其他系统调用相关的技术。书中特别强调了Unix系统设计者的创新思维，如Ken Thompson和Dennis Ritchie的贡献，他们对现代计算机科学的影响是深远的。书中的每个章节都精心编排，如第7章和第12章的详尽解读，不仅教授理论知识，还提供了实际操作的指导。此外，作者在后续版本中不断补充和完善内容，如对MacOS案例研究的深入剖析，关于二进制文件作为缓存的讨论，以及对C语言和异常处理的深入探讨。书中还纠正了一些早期版本中的错误，并增加了对标准库函数如fcntl和ioctl的讨论，这些是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页未读，继续阅读

百無一用是書生

粉丝: 3
资源: 12

Unix编程艺术：经典指南

The Art of Unix Programming

UNIX编程艺术The Art of Unix Programming

The Art of UNIX Programming-Addison-Wesley Professional (2003)Eric S. Raymond

如何利用Knuth的《The Art of Computer Programming》第一册来学习基本的算法和数据结构？

the art of computer programming pdf

Knuth在《The Art of Computer Programming》第一册中如何介绍基础算法和数据结构？请结合实际例子说明。

推荐程序员必读的10本书

Knuth在《The Art of Computer Programming》第一册中如何系统介绍基础算法和数据结构？请结合实际例子详细说明。

the art of r programming pdf

[knu 73] d.e. knuth: the art of computer programming, vol. 3 - s

最新资源