并发编程利器：《Erlang实战》引领你进入并行世界

需积分: 10 155 浏览量更新于2024-07-24 收藏 2.66MB PDF 举报

"《Programming Erlang》是一本由Joe Armstrong编著的专业书籍，专为那些寻求在并发世界中开发软件的读者而设计。该书由图灵图书出版，作为The Pragmatic Bookshelf系列的一部分，它着重强调了Erlang语言在构建高效、并行应用中的关键作用。Erlang被设计为一种特别适合编写并发应用程序的语言，其语法和设计理念有助于开发者模拟现实世界的交互方式和思考模式。本书不仅介绍了Erlang的基础概念，还深入探讨了如何利用它的特性来编写能够处理多线程、分布式系统和高并发负载的程序。通过阅读这本书，读者可以了解到Erlang的轻量级进程模型（Lightweight Processes）、异常处理机制（Behaviours and Callbacks）、以及强大的消息传递系统（Message Passing）等核心要素，这些都使得在编写复杂的并发程序时变得更加简单和可靠。在书中，作者Joe Armstrong以其通俗易懂的写作风格，引导读者逐步掌握Erlang的实践技巧，并分享了他在使用Erlang进行实际项目开发中的经验。此外，他还讨论了如何利用Erlang的并发特性和容错能力来构建具有弹性和鲁棒性的软件架构。值得注意的是，尽管《Programming Erlang》强调了Erlang在处理现代分布式计算中的优势，但它也提醒读者，在使用Erlang时要考虑到版权和商标问题，确保遵循制造商和卖家的产品区分标识规则，避免侵犯知识产权。《Programming Erlang》是一本实用且深入的Erlang编程指南，对于想要在这个高度并行化的时代提高软件开发效率和质量的IT专业人士来说，无疑是一本值得收藏和深入研读的宝贵资源。无论你是初学者还是经验丰富的开发者，都能从中受益匪浅。"

BEGIN AGAIN 16

• Appendix E, on page 419, looks at techniques for analyzing, pr o-

ﬁling, debugging, and tracing your code.

• Appendix F, on page 439, has one-line summaries of the most

sed modules in the Erl ang standard libraries.

1.2 Begin Again

Once upon a time a programmer came across a book describing a funny

programming language. I t had an unfamiliar syntax, equal didn’t mean

equals, and variables weren’t allowed to vary. Worse, it wasn’t even

object-oriented. The programs were, well, different....

Not only were the programs different, but the whole approach to pro-

gramming was different. The author kept on and on about co ncurrency

and distribution and fault tolerance and about a me thod of programming

called concurrency-oriented programming—whatever that might mean.

But some of the examples looked like fun. That evening the programmer

looked at the example chat p rogram. It was pretty small and easy to

understand, even if the syntax was a bit strange. Surely it couldn’t be

that easy.

The basic program was simple, and with a few mo re lines of code, ﬁle

sharing and encrypted conversations became possible. The programmer

started typing....

What’s This All About?

It’s about concurrency. It’s about distribution. It’s about

fault toler-

ance. It’s about functional pr ogramming. It’s about programming a dis-

tributed concurrent system without locks and mutexes but using only

pure message passing. It’s about speeding up your programs on multi-

core CPUs. It’s about writing distributed applications that allow people

to in teract with each other. It’s about design methods and behaviors

for writing fault-tolerant and distributed systems. It’s about modeling

concurrency and mapping those models onto computer programs, a

process I call concurrency-oriented programming.

I had fun writing this book. I hope you have fun reading it.

Now go read the book, write some code, and have fun.

Report erratum

this copy is (P1.1 printing, July, 2007)

www.it-ebooks.info

ACKNOWLEDGMENTS 17

1.3 Acknowledgments

Many people have helped in the preparation of this book, and I’d li ke to

thank them all here.

First, Dave Thomas, my editor: Dave has been t eaching me to write

and subjecting me to a barr age of never-ending questions. Why this?

Why that? When I started the book, Dave said my writing style was like

“standing on a rock preaching.” He said, “I want you to talk to people,

not preach.” The book is better for it. Thanks, Dave.

Next, I’ve had a little committee of l anguage experts at my back. They

helped me decide what to leave out. They also helped me clarify some

of the bits that are difﬁcult to explain. Thanks here (in no particular

order) to Björn Gustavsson, Robert Virding, Kostis Sagonas, Kenneth

Lundin, Richard Carlsson, and Ulf Wiger.

Thanks also to Claes Vikström who provided valuable advice on Mnesia,

to Rickard Green on SMP Erlang, and to Hans Nilsson for the stemming

algorithm used in the text-indexing program.

Sean Hinde and Ulf Wiger helped me understand how t o use various

OTP internals, and Serge Aleynikov explained active sockets to me so

that I could understand.

Helen Taylor (my wife) has proofread several chapters and provided

hundreds of cups of tea at appropriate moments. What’s more, she put

up with my rather obsessive behavior for the last seven months. Thanks

also to Thomas and Claire; and thanks t o Bach and Handel, Zorro and

Daisy, and Doris, who have helped me st ay sane, have purred w hen

stroked, and have gotten me to the right addresses.

Finally, to all the readers of the beta book who ﬁlled in errata requests:

I have cursed you and praised you. When the ﬁrst beta went out, I was

unprepared for the entire book to be read in two days and for you to

shred every page with your comments. But the process has resulted in

a much better book than I had imagined. When (as happened several

times) dozens of people said, “I don’t understand this page,” th en I was

forced to t hink again and rewrite th e material concerned. Thanks for

your help, everybody.

Joe Armstrong

May 2007

Report erratum

this copy is (P1.1 printing, July, 2007)

www.it-ebooks.info

OVERVIEW 19

At this stage you’ll be familiar with Erlang, so we’ll move on to more

interesti ng topics:

• You’ll pick up more advanced uses of t he shell. The shell can do a

lot more than we let on when you were ﬁrst learni ng it. ( For exam-

ple, you can recall and edit previous expressions. This is covered

in Section 6.5, C

ommand Editing in the Erlang Shell, on page 130.)

• You’ll start learning the libraries (called modules in Erlang). Most

of the programs I write can be w ritten using ﬁve modules: lists, io,

ﬁle, dict, and gen_tcp; therefore, we’ll be using these modules a lot

throughout the book.

• As your programs get bigger, you’ll need to l earn how to automate

compiling and running them. The tool of choice for this is make.

We’ll see how to control the process by writing a makeﬁle. This is

covered in Section 6.4, A

utomating Compilation with Makeﬁles, on

page

127.

•

The bigger world of Erlang programming uses an extensive library

collection called OTP.

As you gain experience with Erlang, you’ll

ﬁnd that knowing OTP will save you lots of time. After all, why

reinvent the wheel if someone has already written the functional-

ity you need? We’ll learn the major OTP behaviors, in particular

gen_server. This is covered in Section

16.2, G

etting Started with

gen_server, on page

301.

• One of the main uses of Erlang is writ i ng distributed programs,

so now is the time to start experimenting. You can start with the

examples in Chapter

10, D

istributed Programming, on page 175,

and you can extend them in any way you want.

Stage 2.5: I May Learn Some Optional Stuff

You don’t have to read every chapter in this book the ﬁrst time through.

Unlike most of the languages you have probably met before, Erlang is

a concurrent programming language—this makes it particularly suited

for writing distributed programs and for programming modern multi-

core and SMP

computers. Most Erlang programs will just run faster

when run on a multicore or SMP machine.

Erlang programming in volves using a programming paradigm that I call

concurrency-oriented programming (COP).

1. Open Telecom Platform.

2. Symmetric multiprocessing.

Report erratum

this copy is (P1.1 printing, July, 2007)

www.it-ebooks.info

剩余525页未读，继续阅读

wensee

粉丝: 0
资源: 3

并发编程利器：《Erlang实战》引领你进入并行世界

并发世界中的Erlang编程：Programming Erlang解析

并发编程利器：Programming Erlang.pdf解读

使用Erlang编写高效并发程序：Programming Erlang(2nd版)

《Programming Erlang》

programming erlang src code

Programming Erlang.pdf

Programming Erlang second edition

Programming Erlang 2nd.pdf

Concurrent Programming in ERLANG

erlang programming

最新资源