深入学习JavaScript权威指南第六版

1星需积分: 0 172 浏览量更新于2024-07-23 收藏 13.48MB PDF 举报

"JavaScript权威指南_第6版是David Flanagan撰写的一本深入讲解JavaScript编程语言的专业书籍，适合程序员静下心来仔细研读和学习。该书由O'Reilly Media出版，自1996年以来已经更新至第六版，涵盖了JavaScript语言的最新发展和核心概念。" 在《JavaScript权威指南_第6版》中，作者David Flanagan详尽地探讨了JavaScript的各个方面，旨在帮助读者全面理解并掌握这门广泛应用于网页和互联网应用的脚本语言。以下是一些主要的知识点： 1. **基础语法**：书中首先介绍了JavaScript的基础语法，包括变量、数据类型（如基本类型和引用类型）、运算符、流程控制语句（如条件语句和循环）以及函数的使用。 2. **对象与原型**：JavaScript的核心特性之一是其基于原型的对象模型。书中详细阐述了如何创建和操作对象，以及原型链的工作原理，这对于理解JavaScript中的继承机制至关重要。 3. **函数与闭包**：函数不仅是可执行的代码块，还是JavaScript中的第一等公民，可以作为参数传递和作为返回值。书中深入讨论了函数表达式、作用域、闭包等高级概念，这些都是JavaScript实现模块化和封装的关键。 4. **异步编程**：JavaScript是单线程的，因此异步编程是其处理I/O操作和避免阻塞的关键。书中会介绍事件循环、回调函数、Promise以及现代的async/await语法，帮助开发者理解和利用这些机制。 5. **DOM操作**：作为网页脚本语言，JavaScript与DOM（文档对象模型）紧密相关。书中会讲解如何通过JavaScript来选择、修改和操作HTML元素，实现动态网页效果。 6. **ES6及后续版本的新特性**：第六版涵盖了ECMAScript 6（ES6）及后续版本引入的新功能，如箭头函数、模板字符串、类和模块系统，以及一些性能优化和开发工具的使用。 7. **错误处理与调试**：书中还涉及了如何在JavaScript中捕获和处理错误，以及如何使用开发者工具进行有效的程序调试。 8. **浏览器兼容性**：由于JavaScript的实现存在差异，书中会讨论如何处理跨浏览器兼容性问题，以及如何利用工具和库来简化这一过程。 9. **性能优化**：书中包含了一些关于提高JavaScript代码性能的策略，如减少DOM操作、优化循环和使用适当的数据结构。 10. **安全实践**：最后，书中还会介绍一些JavaScript编程的安全注意事项，比如防止XSS（跨站脚本攻击）和CSRF（跨站请求伪造）等。《JavaScript权威指南_第6版》是一本全面且深入的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页未读，继续阅读

方小木

粉丝: 1
资源: 5

深入学习JavaScript权威指南第六版

JavaScript权威指南_第6版 含源码

JavaScript权威指南_第6版 中文版

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

javascript权威指南(第7版) pdf

javascript权威指南mobi

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

javascript权威指南

JavaScript函数 p_del()的用法

css权威指南第四版 数据库

javascript高级程序设计第五版 pdf

最新资源

JavaScript权威指南_第6版含源码

JavaScript权威指南_第6版中文版

css权威指南第四版数据库