- Taschenbuch: 494 Seiten
- Verlag: O'Reilly and Associates; Auflage: 1 (15. Juli 2009)
- Sprache: Englisch
- ISBN-10: 0596518188
- ISBN-13: 978-0596518189
- Größe und/oder Gewicht: 17,8 x 2,8 x 23,3 cm
- Durchschnittliche Kundenbewertung: 2 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 78.423 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Erlang Programming (Englisch) Taschenbuch – 15. Juli 2009
|Neu ab||Gebraucht ab|
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre E-Mail-Adresse oder Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Mehr über die AutorenEntdecken Sie Bücher, lesen Sie über Autoren und mehr
The book provides an in depth explanation of the basics and essentials of Erlang. All readers, regardless of programming background or level, should be grasp what Erlang is all about after reading this book. They should be able to write fairly complex concurrent programs. The book focuses the syntax and semantics of the language, explaining pattern matching, proper lists, recursion, and concurrency. Erlang is a 'new' technology on the brink of adoption. Fuelled by industry trends, blogs, commercial success stories, and the increasing importance of concurrent programming, there is a market for Erlang/OTP related books on all levels waiting to be exploited. Interest in and excitement about Erlang (and other functional programming languages, like Haskell) has been very much on the rise.
Über den Autor und weitere Mitwirkende
Francesco Cesarini is the founder and CTO of Erlang Training and Consulting. Having used Erlang on a daily basis since 1995, he started his career as an intern at Ericsson's computer science lab, the birth place of Erlang. He spent four years at Ericsson working with flagship Erlang projects, including the R1 release of the OTP middleware. He has taught Erlang/OTP to all parties involved in the software cycle, including developers, support engineers, testers as well as project and technical managers. In 2003, he also started teaching undergraduate students at the IT University of Gothenburg. Soon after Erlang was released as Open Source, he founded Erlang Training and Consulting. With offices in the UK, Sweden, Poland (and soon the US), they have become the world leaders in Erlang based consulting, contracting, support, training and systems development. Their client base is spread on five continents and ranges from small start-ups to blue chip companies. In his role as CTO, is currently leading the research, development and consulting teams. He is active in the Erlang community not only through regularly talks, seminars and tutorials at conferences worldwide, but also through his involvement in international research projects. He organises local Erlang user groups and with the help of his colleagues, runs the trapexit.org Erlang community website. Simon Thompson is Professor of Logic and Computation in the Computing Laboratory of the University of Kent, where he has taught computing at undergraduate and postgraduate levels for the past twenty five years, and where he has been department head for the last six. His research work has centered on functional programming: program verification, type systems, and most recently development of software tools for functional programming languages. His team has built the HaRe tool for refactoring Haskell programs, and is currently developing Wrangler to do the same for Erlang. His research has been funded by various agencies including EPSRC and the European Framework programme. His training is as a mathematician: he has an MA in Mathematics from Cambridge and a D.Phil. in mathematical logic from Oxford. He has written three books in his field of interest; Type Theory and Functional Programming published in 1991; Miranda: The Craft of Functional Programming (1995) and Haskell: The Craft of Functional Programming (2nd ed. 1999). These are all published by Addison Wesley.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch(Mehr dazu)
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
This book is written for experienced programmers, but not necessarily those that have any prior exposure to Erlang or even functional programming languages in general. The book consists of two parts. The first should be read sequentially, like a textbook. The second part, however, can be read in any order as you need the informaton. The following is a listing of the chapters and a brief description of what you'll find in each.
The first part of the book consists of the first eleven chapters, and describes the core parts of the Erlang language.
1. Introduction - Gives a high-level overview of the characteristics and features that have made Erlang so successful, provides insight into the context in which the language was designed, and describes how this influenced its current shape. Case studies show how Erlang is actually used, comparing it with other languages and highlighting its strengths.
2. Erlang Basics - Covers the basics of Erlang. Some of this will be elementary for experienced programmers, and some will not, such as the fact that you can assign to each variable only once. The chapter starts with defining the basic Erlang data types, and concludes by showing how to define Erlang functions and place them into modules to create programs.
3. Sequential Erlang - An important topic here is recursion, which is perhaps the most useful and powerful of all techniques usually found in a functional language. It allows a programmer to traverse a data structure via successive calls to the same function. Also exception-handling mechanisms are covered here as is the debugger.
4. Concurrent Programming - Concurrency is when different functions execute in parallel without affecting each other unless explicitly programmed to do so. The ability of the runtime system to scale concurrency to levels such that there can be thousands of processes running in parallel with a small memory footprint differentiates Erlang from other concurrent programming languages. This chapter discusses all of these matters.
5. Process Design Patterns - Many Erlang processes will fall into one of three categories - client/servers, finite state machines, and event handlers. This chapter looks at examples of process design patterns, explaining how they can be used to program each of these three types of processes. The OTP framewor is also part of this topic, but OTP doesn't get discussed until chapter 12.
6. Process Error Handling - Erlang has simple but powerful constructs built into the language's concurrency model. These constructs allow processes to monitor each other's behavior and to recover from software faults, and are discussed here.
7. Records and Macros - In the first part of this chapter you will learn about records, which make code evolution easier to achieve. The key to this is the fact that records provide data abstraction. Macros, the other topic in this chapter, allow you to write abbreviations that are expanded by the Erlang preprocessor. Macros can be used to make programs more readable, to extend the language, and to write debugging code. The chapter concludes by describing the include directive, by which header files containing macro and record definitions are used in Erlang projects.
8. Software Upgrade - The software upgrade mechanism relies on a set of simple but powerful constructs upon which more powerful tools are built. These upgrade tools are used in pretty much every Erlang-based system where downtime has to be reduced to a minimum. These topics are explored here.
9. More data types and high-level constructs - The various language features covered in this chapter, many of them derived from functional programming languages, are tools that will improve the productivity of a working Erlang programmer. The topics are: funs and higher-order functions, list comprehensions, binaries, and serialization.
10. ETS and Dets Tables - To handle fast searches, Erlang provides two mechanisms. This chapter introduces Erlang Term Storage (ETS) and Disk Erlang Term Storage (Dets), two mechanisms for memory and disk-efficient storage and retrieval of large groups of data. Erlang also provides a full database application, Mnesia, which is covered in chapter 13.
11. Distributed Programming in Erlang - This chapter explores the theory behind distributed systems and shows how it is applied to Erlang-based systems. Erlang distribution is built into the language, and can be completely transparent to the user.
The rest of the book can be read in any order as needed:
12. OTP Behaviors - OTP behaviors provide library modules that implement the most common concurrent design patterns. Behind the scenes the library modules insure that errors and special cases are handled in a consistent way. As a result, OTP behaviors provide a set of standardized building blocks. This subject is a large one and this chapter is only an introduction.
13. Introducing Mnesia - Mnesia is a powerful database that is part of the standard Erlang distribution. It merges the efficiency and simplicity of ETS and Dets tables with the Erlang distribution and adds a transaction layer on top. Again, this is a large subject and this chapter acts only as an introduction.
14. GUI Programming with Erlang - GUIs are not one of Erlang's strengths, but it does have a cross-platform GUI programming system, wxErlang, which is a binding of the wxWidgets system. This chapter introduces wxWidgets and explains its Erlang binding. After describing the event-handling mechanism in wxErlang, a scaled-down blog example is presented using it. This chapter concludes with a number of pointers for learning more about wxWidgets and wxErlang, and a series of exercises to improve and extend the running example.
15. Socket Programming - Sockets allow programs written in any language to exchange data on different computers by exchanging byte streams transmitted using the protocols of the Internet Protocol. Sometimes even Erlang programs must rely on such a lower-level mechanism for communication.
16. Interfacing Erlang with Other Programming Languages - Discusses how to link Erlang with a C program, Java program, or the Unix shell.
17. Trace BIFs, the dbg Tracer, and Match Specifications - Explains in depth how all aspects of Erlang systems can be traced without degrading their performance.
18. Types and Documentation - This chapter shows how you can write down the types of functions as a part of their formal documentation in Erlang, using the EDoc documentation framework. In addition, what you write down as the type of a function can be checked for consistency against the function definition using the TypEr tool, which is also discussed here.
19. EUnit and Test-Driven Development - In this chapter, the EUnit tool, which gives you a framework for unit testing in Erlang, is discussed. It is shown in action and there is a discussion on how it supports test-driven development.
20. Styles and Efficiency - Summarizes design guidelines and programming strategies to use when developing Erlang systems. The chapter also covers common mistakes and inefficiencies and looks at memory handling and profiling.
Appendix A - Using Erlang- Recommends tools to help you in Erlang softare development and also lists resources for programmers such as websites and books.
I've spent some considerable time with both Haskell and Erlang, two very good functional languages. When it comes to high concurrency and networking applications, Erlang is probably the best choice. However, I still like Haskell because I've found it easier to handle when writing multimedia applications, which is often my focus. You could take a long time to come to your own conclusions, but I found this book and the recently published book on Haskell, Real World Haskell, to cut that time down extensively by explaining the features of both languages so well. I therefore highly recommend this book to people trying to make up their minds about Erlang and those that have made up their minds and now need a clear book on the subject.
By all means, get all three books: 'Programming Erlang' (Pragmatic) by Joe Armstrong, 'Erlang and OTP in Action' (Manning) by Martin Logan et. al., and this book by Francesco and Simon. But if you choose to buy only one, I do not hesitate to recommend this one. But do yourself a favor and get all three. Each one offers a different perspective.
I am fairly new to Erlang and unfortunately do not use it in my daily job (SAP technical consultant by day) so I can only give a "beginners viewpoint". Not taking anything away from Joe Armstrongs book at all...it is also superb, but from a beginners point of view I have found that "Erlang Programming" is an easier read and I'm doing more "oh, is that how it works" now ;-) I especially enjoy the little diagrams scattered around the book to help illustrate how the processes communicate etc.
The chapters I have found most useful to me are:
- Process Design Patterns (I enjoyed reading on the "Finite State Machine etc")
- Process Error Handling
- Distributed Programming in Erlang
Overall I am VERY impressed with this book and would happily recommend it to anyone like me who is trying to get up to speed with Erlang very quickly.
BTW: The 2 books combined definetly compliment each other very nicely!
Thankyou Simon and Francesco for an OUTSTANDING book!!
The authors have done a good job of motivating the reader in the first couple of chapters.
These are followed by a few more that lay out the foundations of the language in a crisp and concise manner.
The next set of chapters on processes and their design patterns are informative and interesting.
The last chapters concentrate on describing the libraries provided by the OTP platform including one on the battle-tested Mnesia database.
Overall, I'd say it's a well organized and easy read.
I've only just started with Erlang and am enjoying it quite a bit - other than wondering if this is another one of those flash-in-the-pan languages. Even if Erlang is not long lived, I think that something like Erlang is where computing is destined to go. The reason being that even our supercomputers seem to have moved away from big iron and into the cluster world. Erlang fits onto clusters more naturally than anything I've yet experienced and that includes MPI and PVM. The reason is that Erlang provides the infrastructure for running an awe inspiring number of "processes" in a multi-machine environment. Or on one machine if that's your preference. Process is in quote marks above because each process runs in an erlang VM instead of as a process/thread in the operating system.
The thing that really amazes me about Erlang is how easy it is to design and build stuff that is fault tolerant and that scales unbelievably. It really is beautiful. I'm kinda wondering if Erlang is the destined to be the "glue language" for clusters.
As for direct usefulness of the book... I've read chapters: 1 Intro; 2 Erlang Basics; 3 Sequential Erlang; 4 Concurrent Programming; and 11 Distributed Programming. In that order. It was a few hours of reading and fiddling around and now I'm somewhat dangerously able to use the language for what I want. Gotta read those other chapters though.
So, why read the chapters? It's because the writing is honest and applicable. Kind of like the bit in Chapter 2 (I think) where the author says you should mess around with something error prone in the shell now because the next time it'll be buried deep in some module and be difficult to isolate. Now that's practical. I bet that OTP chapter will keep me from reinventing some wheels too.