JavaScript权威指南（第六版）：从入门到精通

需积分: 50 5 浏览量更新于2024-07-24 收藏 13.48MB PDF 举报

"《JavaScript权威指南》(Sixth Edition) 是由David Flanagan撰写的一本经典著作，专为JavaScript编程语言的学习者设计。本书是该系列的第六版，自1996年首版以来，历经多次更新，反映了JavaScript语言的不断发展和变化。作为一本权威指南，它深入浅出地介绍了JavaScript的基础概念、语法特性、DOM操作、事件处理、异步编程、函数式编程以及Web应用开发的相关技术。在书中，作者从基础出发，涵盖了JavaScript的各个方面，包括变量与数据类型、控制结构（如循环和条件语句）、函数和对象，帮助读者建立起坚实的编程基础。对于JavaScript的核心对象，如Array、Date、JSON等，都有详尽的阐述。此外，书中还特别关注了浏览器环境中的JavaScript，包括DOM操作，这在构建现代Web应用时至关重要。随着JavaScript在Web开发中的地位日益提升，书中还讲解了如何利用AJAX实现与服务器的异步通信，以及Node.js环境下的服务器端JavaScript开发。书中还提到了ECMAScript标准的演变，让读者了解JavaScript语言的最新规范和最佳实践。第六版还可能包含了一些新的JavaScript框架和库的介绍，比如jQuery的使用，以及如何编写模块化代码和使用ES6新特性，如箭头函数、模板字符串等。为了便于查找和理解，每章末尾通常会有详细的索引，方便读者快速定位所需信息。作为一本专业级的参考书籍，《JavaScript权威指南》不仅适合初学者系统学习JavaScript，也适合有一定基础的开发者查阅和巩固知识。无论是想深入了解JavaScript语言，还是希望提升Web开发技能，这本书都是不可或缺的资源。无论是纸质版还是在线版本，都能提供丰富的实例和练习，帮助读者在实践中不断提升编程能力。"

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页未读，继续阅读

alan999cy

粉丝: 0
资源: 6

JavaScript权威指南（第六版）：从入门到精通

JavaScript权威指南（第五版）

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

javascript权威指南_高清版pdf_1

JavaScript权威指南

javaScript 权威指南

javascript 权威指南

Javascript权威指南

脑机接口电路与系统 Amir

WaCRM：提升电商独立站用户的WhatsApp营销利器安装文件v3.1.0.zip

[文件]作业帮试卷上传.pdf

最新资源