高清英文第六版 | JavaScript权威指南详解

5星 · 超过95%的资源需积分: 50 79 浏览量更新于2024-07-25 收藏 13.48MB PDF 举报

"《JavaScript权威指南》第六版（高清英文版）是一本由David Flanagan编写的经典著作，专为深入理解JavaScript编程语言而设计。本书作为该领域的权威指南，自1996年首版以来历经多次更新，直至2011年的第六版，持续反映了JavaScript语言的发展和变化。本书的特点在于其高清质量的英文版，使得学习者无论在阅读体验还是信息获取上都能获得极佳的视觉效果。《JavaScript权威指南》覆盖了广泛的JavaScript知识，包括但不限于：语言基础、DOM操作、事件处理、函数式编程、对象和类、异步编程、模块化、浏览器兼容性以及现代框架如Node.js等。对于初学者，它提供了详尽的入门指导；对于经验丰富的开发者，它则是深入探究JavaScript核心特性和最佳实践的宝典。此书的第六版特别注重实用性，不仅包含了JavaScript语法的最新特性，还探讨了如何编写高效、可维护的代码。编辑Mike Loukides与生产编辑Teresa Elsey共同协作，确保内容的准确性和流畅度。书中还包含严格的校对工作，由Proofreader Teresa Elsey负责，确保每一处细节都经过精心审查。此外，专门的Indexer Ellen Troutman Zaig负责索引，方便读者快速查找所需信息。封面设计由Karen Montgomery操刀，内部设计则由David Futato负责，整体风格既专业又易于阅读。插图由Robert Romano绘制，进一步增强了视觉效果和理解。印刷历史显示了本书自1996年Beta版以来不断迭代和改进的过程，反映出作者和出版商对JavaScript技术的持续关注和投入。无论你是希望提升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页未读，继续阅读

小十一月

粉丝: 3
资源: 3

高清英文第六版 | JavaScript权威指南详解

JavaScript权威指南(第六版) 清晰-完整

JavaScript权威指南（第六版）

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

javascript权威指南(第7版) pdf

javascript权威指南mobi

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

javascript第六版电子书

javascript权威指南

css权威指南第四版 数据库

html5权威指南下载

最新资源

css权威指南第四版数据库