JavaScript权威指南(第6版)英文版：深度解析

需积分: 31 146 浏览量更新于2024-07-27 收藏 13.48MB PDF 举报

"JavaScript权威指南(第6版) 英文版" JavaScript是Web开发中的核心技术之一，由David Flanagan编写的《JavaScript权威指南(第6版)》是一本广泛认可的经典教材。这本书深入探讨了JavaScript语言的各个方面，旨在帮助读者全面理解并熟练掌握JavaScript编程。本书覆盖了以下关键知识点： 1. **基础语法**: 包括变量、数据类型（如字符串、数字、布尔值、null、undefined、对象和数组）、操作符、流程控制（条件语句、循环）、函数和表达式。 2. **对象和原型**: 详细介绍了JavaScript的基于原型的对象模型，包括对象创建、属性访问、原型链以及如何使用构造函数和原型对象进行面向对象编程。 3. **闭包和作用域**: 解释了JavaScript中的作用域规则，以及闭包如何在内存管理中起到关键作用，同时讨论了如何利用它们来实现模块化和私有变量。 4. **异步编程**: 讲解了事件循环、回调函数、Promise和async/await，这些都是处理非阻塞I/O和网络通信的关键技术。 5. **DOM操作**: 详细阐述了如何使用JavaScript与HTML文档对象模型交互，包括元素选择、添加、删除和修改HTML内容，以及事件处理。 6. **错误处理**: 介绍了如何使用try...catch语句处理运行时错误，并讨论了错误对象和异常处理的最佳实践。 7. **ES6及以后的版本特性**: 包括箭头函数、模板字符串、类、let和const、解构赋值、模块系统等新特性，这些都极大地扩展了JavaScript的功能和可读性。 8. **性能优化**: 提供了编写高效JavaScript代码的技巧，包括避免全局变量、减少DOM操作、优化循环和使用缓存等。 9. **调试和测试**: 介绍如何使用开发者工具进行代码调试，以及如何编写单元测试来确保代码质量。 10. **浏览器兼容性**: 考虑到JavaScript在不同浏览器中的实现差异，书中会讲解如何处理兼容性问题，确保代码在多种环境下正常运行。《JavaScript权威指南(第6版)》不仅适合初学者入门，也适合有经验的开发者深入学习。它不仅包含详细的语法解析，还有大量示例和实用建议，使得读者能够更好地理解和应用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页未读，继续阅读

baojieearth

粉丝: 3
资源: 4

JavaScript权威指南(第6版)英文版：深度解析

JavaScript权威指南(第6版)(中文版)

[JavaScript] JavaScript 权威指南 第6版 (英文版)

Javascript权威指南第6版(英文文字版)

JavaScript 权威指南第6版

JavaScript权威指南第6版

JavaScript权威指南 第6版

JavaScript权威指南 第6版 中文版

基于springboot共享经济背景下校园闲置物品交易平台源码数据库文档.zip

基于WoodandBerry1和非耦合控制WoodandBerry2来实现控制木材和浆果蒸馏柱控制Simulink仿真.rar

emcopy042002.zip

最新资源

[JavaScript] JavaScript 权威指南第6版 (英文版)

JavaScript权威指南第6版

JavaScript权威指南第6版中文版