JavaScript权威指南：第六版

需积分: 34 119 浏览量更新于2024-07-22 收藏 13.48MB PDF 举报

"JavaScript权威指南第六版" 《JavaScript权威指南》是David Flanagan撰写的一本经典JavaScript参考书籍，适合网页和游戏开发人员使用。这本书全面深入地探讨了JavaScript语言的各个方面，为开发者提供了必备的知识库。本书第六版在2011年由O'Reilly Media出版，覆盖了JavaScript的最新发展和特性。作者David Flanagan是一位知名的编程专家，他的作品以其准确性和深度而受到业界的广泛认可。书中内容可能包括但不限于以下几个关键知识点： 1. **基础语法**：讲解JavaScript的基本语法结构，如变量、数据类型（包括基本类型和引用类型）、运算符、流程控制（条件语句和循环）以及函数的使用。 2. **对象与原型**：深入解析JavaScript的对象模型，包括对象创建、原型链、继承机制以及构造函数等概念。 3. **作用域与闭包**：解释JavaScript中的变量作用域规则，以及闭包如何提供对私有变量的访问和实现函数间的记忆。 4. **函数表达式与立即调用的函数表达式(IIFE)**：介绍函数作为值的特性，以及IIFE用于封装代码和避免全局污染的方法。 5. **事件处理**：讨论DOM（文档对象模型）中的事件处理机制，包括事件监听器、事件冒泡和事件捕获。 6. **异步编程**：讲解回调函数、Promise和async/await等处理异步操作的方式，以及如何解决回调地狱问题。 7. **正则表达式**：深入正则表达式的模式匹配，包括元字符、量词、分组和捕获等高级特性。 8. **DOM操作**：如何通过JavaScript来查找、修改和添加DOM元素，以及如何处理DOM树的变动。 9. **AJAX与Fetch API**：介绍异步获取远程数据的技术，包括XMLHttpRequest的使用和现代Fetch API的实现。 10. **ES6及以后的新特性**：涵盖ES6（ECMAScript 2015）引入的箭头函数、模板字符串、类、模块系统等新特性，以及后续版本的更新。 11. **错误处理**：讨论如何有效地处理运行时错误，包括try...catch语句和自定义错误对象。 12. **性能优化**：提供关于代码性能的指导，包括避免内存泄漏、减少DOM操作和优化循环等技巧。 13. **调试与测试**：介绍如何使用开发者工具进行JavaScript代码的调试，以及单元测试和集成测试的重要性。此外，书中的索引和目录系统帮助读者快速定位所需的信息，而专业的编辑和设计团队确保了内容的清晰度和易读性。通过阅读《JavaScript权威指南》，开发者能够获得全面且权威的JavaScript知识，从而提升他们的编程技能和项目开发能力。

A Note About Piracy

If you are reading a digital version of this book that you (or your employer) did not pay

for (or borrow from someone who did) then you probably have an illegally pirated copy.

Writing the sixth edition of this book was a full-time job, and it took more than a year.

The only way I get paid for that time is when readers actually buy the book. And the

only way I can afford to work on a seventh edition is if I get paid for the sixth.

I do not condone piracy, but if you have a pirated copy, go ahead and read a couple of

chapters. I think that you’ll find that this is a valuable source of information about

JavaScript, better organized and of higher quality than what you can find freely (and

legally) available on the Web. If you agree that this is a valuable source of information,

then please pay for that value by purchasing a legal copy (either digital or print) of the

book. On the other hand, if you find that this book is no more valuable than the free

information on the web, then please discard your pirated copy and use those free

information sources.

Conventions Used in This Book

I use the following typographical conventions in this book:

Italic

Is used for emphasis and to indicate the first use of a term. Italic is also used for

email addresses, URLs and file names.

Constant width

Is used in all JavaScript code and CSS and HTML listings, and generally for any-

thing that you would type literally when programming.

Constant width italic

Is used for the names of function parameters, and generally as a placeholder to

indicate an item that should be replaced with an actual value in your program.

Example Code

The examples in this book are available online. You can find them linked from the

book’s catalog page at the publisher’s website:

http://oreilly.com/catalog/9780596805531/

This book is here to help you get your job done. In general, you may use the code in

this book in your programs and documentation. You do not need to contact O’Reilly

for permission unless you’re reproducing a significant portion of the code. For example,

writing a program that uses several chunks of code from this book does not require

permission. Selling or distributing a CD-ROM of examples from O’Reilly books does

require permission. Answering a question by citing this book and quoting example

xiv | Preface

code does not require permission. Incorporating a significant amount of example code

from this book into your product’s documentation does require permission.

If you use the code from this book, I appreciate, but do not require, attribution. An

attribution usually includes the title, author, publisher, and ISBN. For example: “Java-

nagan, 978-0-596-80552-4.”

For more details on the O’Reilly code reuse policy, see http://oreilly.com/pub/a/oreilly/

ask_tim/2001/codepolicy.html. If you feel your use of the examples falls outside of the

permission given above, feel free to contact O’Reilly at permissions@oreilly.com.

Errata and How to Contact Us

The publisher maintains a public list of errors found in this book. You can view the

list, and submit the errors you find, by visiting the book’s web page:

http://oreilly.com/catalog/9780596805531

To comment or ask technical questions about this book, send email to:

bookquestions@oreilly.com

For more information about our books, conferences, Resource Centers, and the

O’Reilly Network, see our website at:

http://www.oreilly.com

Find us on Facebook: http://facebook.com/oreilly

Watch us on YouTube: http://www.youtube.com/oreillymedia

Acknowledgments

Many people have helped me with the creation of this book. I’d like to thank my editor,

Mike Loukides, for trying to keep me on schedule and for his insightful comments.

Thanks also to my technical reviewers: Zachary Kessin, who reviewed many of the

chapters in Part I, and Raffaele Cecco, who reviewed Chapter 19 and the <canvas>

material in Chapter 21. The production team at O’Reilly has done their usual fine job:

Dan Fauxsmith managed the production process, Teresa Elsey was the production

editor, Rob Romano drew the figures, and Ellen Troutman Zaig created the index.

In this era of effortless electronic communication, it is impossible to keep track of all

those who influence and inform us. I’d like to thank everyone who has answered my

questions on the es5, w3c, and whatwg mailing lists, and everyone who has shared their

insightful ideas about JavaScript programming online. I’m sorry I can’t list you all by

Preface | xv

JavaScript: Names and Versions

JavaScript was created at Netscape in the early days of the Web, and technically, “Java-

Script” is a trademark licensed from Sun Microsystems (now Oracle) used to describe

Netscape’s (now Mozilla’s) implementation of the language. Netscape submitted the

language for standardization to ECMA—the European Computer Manufacturer’s As-

sociation—and because of trademark issues, the standardized version of the language

was stuck with the awkward name “ECMAScript.” For the same trademark reasons,

Microsoft’s version of the language is formally known as “JScript.” In practice, just

about everyone calls the language JavaScript. This book uses the name “ECMAScript”

only to refer to the language standard.

For the last decade, all web browsers have implemented version 3 of the ECMAScript

standard and there has really been no need to think about version numbers: the lan-

guage standard was stable and browser implementations of the language were, for the

most part, interoperable. Recently, an important new version of the language has been

defined as ECMAScript version 5 and, at the time of this writing, browsers are beginning

to implement it. This book covers all the new features of ECMAScript 5 as well as all

the long-standing features of ECMAScript 3. You’ll sometimes see these language ver-

sions abbreviated as ES3 and ES5, just as you’ll sometimes see the name JavaScript

abbreviated as JS.

When we’re speaking of the language itself, the only version numbers that are relevant

are ECMAScript versions 3 or 5. (Version 4 of ECMAScript was under development

for years, but proved to be too ambitious and was never released.) Sometimes, however,

you’ll also see a JavaScript version number, such as JavaScript 1.5 or JavaScript 1.8.

These are Mozilla’s version numbers: version 1.5 is basically ECMAScript 3, and later

versions include nonstandard language extensions (see Chapter 11). Finally, there are

also version numbers attached to particular JavaScript interpreters or “engines.” Goo-

gle calls its JavaScript interpreter V8, for example, and at the time of this writing the

current version of the V8 engine is 3.0.

To be useful, every language must have a platform or standard library or API of func-

tions for performing things like basic input and output. The core JavaScript language

defines a minimal API for working with text, arrays, dates, and regular expressions but

does not include any input or output functionality. Input and output (as well as more

sophisticated features, such as networking, storage, and graphics) are the responsibility

of the “host environment” within which JavaScript is embedded. Usually that host

environment is a web browser (though we’ll see two uses of JavaScript without a web

browser in Chapter 12). Part I of this book covers the language itself and its minimal

built-in API. Part II explains how JavaScript is used in web browsers and covers the

sprawling browser-based APIs loosely known as “client-side JavaScript.”

Part III is the reference section for the core API. You can read about the JavaScript array

manipulation API by looking up “Array” in this part of the book, for example.

Part IV is the reference section for client-side JavaScript. You might look up “Canvas”

2 | Chapter 1: Introduction to JavaScript

剩余1097页未读，继续阅读

liu-c123

粉丝: 0
资源: 5

JavaScript权威指南：第六版

JavaScript权威指南（第五版）

JavaScript权威指南（JavaScript犀牛书一本）

javascript权威指南_高清版pdf_1

javascript权威指南mobi

javascript权威指南(第7版) pdf

javascript 权威指南第7版_第七版 JavaScript权威指南之标准库

javascript权威指南(第7版)\ filetype pdf"

javascript权威指南

javascript参考文献

javaScript相关电子书

最新资源