Core Java 8th Vol I: 入门指南

5星 · 超过95%的资源需积分: 10 4 浏览量更新于2024-07-30 收藏 18.54MB PDF 举报

"Core Java 8th Vol I - 经典的Java教程，涵盖Java基础的第八版，提供高质量的英文PDF版本。" 《Core Java 8th Vol I》是Java编程领域的一本经典教程，专注于Java语言的基础知识。这本书由Cay S. Horstmann和Gary Cornell合著，由Sun Microsystems Press出版，旨在帮助读者深入理解Java 8的核心概念和技术。该书内容广泛，涵盖了Java开发所需的关键技能。在Java 8中，最重要的更新之一是引入了lambda表达式，这是一种简洁、强大的函数式编程工具，使得处理集合数据更加高效。Lambda表达式允许开发者以匿名函数的形式传递代码，简化了回调和事件处理，尤其在并行处理和Stream API中得到了广泛应用。Stream API是Java 8的另一个亮点，它提供了对集合进行声明式处理的能力，支持过滤、映射、聚合等操作，极大地提升了代码的可读性和性能。书中还详细讲解了泛型，这是Java 5引入的重要特性，用于在编译时提供类型安全，避免了运行时的类型转换异常。泛型在类、接口和方法中的应用，以及通配符和类型推断等高级用法，都是学习Java不可或缺的部分。此外，Java 8对日期和时间API进行了彻底的重构，推出了java.time包，取代了原有的java.util.Date和Calendar类，提供了更直观、更易用的API，处理日期和时间变得更加方便。书中会详细介绍LocalDate、LocalTime、LocalDateTime等类的使用。反射是Java的一个强大特性，允许在运行时检查和修改程序的行为。《Core Java 8th Vol I》会介绍如何使用反射来访问类、接口、构造器和方法，以及如何动态创建对象和调用方法。异常处理是Java编程中的重要组成部分，本书将深入讲解如何正确地使用try-catch-finally语句块，理解checked和unchecked异常的区别，以及如何设计和使用自定义异常。多线程是Java的一大特色，书中会涵盖线程的基本概念、同步机制（如synchronized关键字和Lock接口）、并发工具类（如ExecutorService和Future），以及如何避免并发问题。除此之外，书中还会讨论网络编程、I/O流、数据库连接、XML处理、JDBC、Swing GUI开发等方面的内容，这些都是Java开发者必备的知识。《Core Java 8th Vol I》是一本全面覆盖Java 8基础知识的教程，无论你是初学者还是有经验的开发者，都能从中获得宝贵的指导和启示，提升你的Java编程能力。

Chapter 1

■

An Introduction to Java

he first release of Java in 1996 generated an incredible amount of excitement, not

just in the computer press, but in mainstream media such as The New York Times, The

Washington Post, and Business Week. Java has the distinction of being the first and only

programming language that had a ten-minute story on National Public Radio. A

$100,000,000 venture capital fund was set up solely for products produced by use of a

specific computer language. It is rather amusing to revisit those heady times, and we

give you a brief history of Java in this chapter.

Java As a Programming Platform

In the first edition of this book, we had this to write about Java:

“As a computer language, Java’s hype is overdone: Java is certainly a good program-

ming language. There is no doubt that it is one of the better languages available to

serious programmers. We think it could potentially have been a great programming

language, but it is probably too late for that. Once a language is out in the field, the ugly

reality of compatibility with existing code sets in.”

Our editor got a lot of flack for this paragraph from someone very high up at Sun Micro-

systems who shall remain unnamed. But, in hindsight, our prognosis seems accurate.

Java has a lot of nice language features—we examine them in detail later in this chapter.

It has its share of warts, and newer additions to the language are not as elegant as the

original ones because of the ugly reality of compatibility.

But, as we already said in the first edition, Java was never just a language. There are lots

of programming languages out there, and few of them make much of a splash. Java is a

whole platform, with a huge library, containing lots of reusable code, and an execution

environment that provides services such as security, portability across operating sys-

tems, and automatic garbage collection.

As a programmer, you will want a language with a pleasant syntax and comprehensible

semantics (i.e., not C++). Java fits the bill, as do dozens of other fine languages. Some

languages give you portability, garbage collection, and the like, but they don’t have

much of a library, forcing you to roll your own if you want fancy graphics or network-

ing or database access. Well, Java has everything—a good language, a high-quality exe-

cution environment, and a vast library. That combination is what makes Java an

irresistible proposition to so many programmers.

The Java “White Paper” Buzzwords

The authors of Java have written an influential White Paper that explains their design

goals and accomplishments. They also published a shorter summary that is organized

along the following 11 buzzwords:

Simple Portable

Object Oriented Interpreted

Network-Savvy High Performance

Robust Multithreaded

Secure Dynamic

Architecture Neutral

Chapter 1. An Introduction to Java

The Java “White Paper” Buzzwords

In this section, we will

• Summarize, with excerpts from the White Paper, what the Java designers say about

each buzzword; and

• Tell you what we think of each buzzword, based on our experiences with the cur-

rent version of Java.

NOTE: As we write this, the White Paper can be found at http://java.sun.com/docs/white/

langenv/. The summary with the 11 buzzwords is at http://java.sun.com/docs/overviews/java/

java-overview-1.html.

Simple

We wanted to build a system that could be programmed easily without a lot of eso-

teric training and which leveraged today’s standard practice. So even though we

found that C++ was unsuitable, we designed Java as closely to C++ as possible in

order to make the system more comprehensible. Java omits many rarely used, poorly

understood, confusing features of C++ that, in our experience, bring more grief

than benefit.

The syntax for Java is, indeed, a cleaned-up version of the syntax for C++. There is no

need for header files, pointer arithmetic (or even a pointer syntax), structures, unions,

operator overloading, virtual base classes, and so on. (See the C++ notes interspersed

throughout the text for more on the differences between Java and C++.) The designers

did not, however, attempt to fix all of the clumsy features of C++. For example, the syn-

tax of the

switch

statement is unchanged in Java. If you know C++, you will find the tran-

sition to the Java syntax easy.

If you are used to a visual programming environment (such as Visual Basic), you will

not find Java simple. There is much strange syntax (though it does not take long to get

the hang of it). More important, you must do a lot more programming in Java. The

beauty of Visual Basic is that its visual design environment almost automatically pro-

vides a lot of the infrastructure for an application. The equivalent functionality must be

programmed manually, usually with a fair bit of code, in Java. There are, however,

third-party development environments that provide “drag-and-drop”-style program

development.

Another aspect of being simple is being small. One of the goals of Java is to enable

the construction of software that can run stand-alone in small machines. The size of

the basic interpreter and class support is about 40K bytes; adding the basic stan-

dard libraries and thread support (essentially a self-contained microkernel) adds an

additional 175K.

This was a great achievement at the time. Of course, the library has since grown to huge

proportions. There is now a separate Java Micro Edition with a smaller library, suitable

for embedded devices.

Object Oriented

Simply stated, object-oriented design is a technique for programming that focuses

on the data (= objects) and on the interfaces to that object. To make an analogy with

carpentry, an “object-oriented” carpenter would be mostly concerned with the chair

Chapter 1. An Introduction to Java

Chapter 1

■

An Introduction to Java

he was building, and secondarily with the tools used to make it; a “non-object-

oriented” carpenter would think primarily of his tools. The object-oriented facilities

of Java are essentially those of C++.

Object orientation has proven its worth in the last 30 years, and it is inconceivable that a

modern programming language would not use it. Indeed, the object-oriented features of

Java are comparable to those of C++. The major difference between Java and C++ lies in

multiple inheritance, which Java has replaced with the simpler concept of interfaces,

and in the Java metaclass model (which we discuss in Chapter 5).

NOTE: If you have no experience with object-oriented programming languages, you will

want to carefully read Chapters 4 through 6. These chapters explain what object-oriented

programming is and why it is more useful for programming sophisticated projects than are

traditional, procedure-oriented languages like C or Basic.

Network-Savvy

Java has an extensive library of routines for coping with TCP/IP protocols like

HTTP and FTP. Java applications can open and access objects across the Net via

URLs with the same ease as when accessing a local file system.

We have found the networking capabilities of Java to be both strong and easy to use.

Anyone who has tried to do Internet programming using another language will revel in

how simple Java makes onerous tasks like opening a socket connection. (We cover net-

working in Volume II of this book.) The remote method invocation mechanism enables

communication between distributed objects (also covered in Volume II).

Robust

Java is intended for writing programs that must be reliable in a variety of ways.

Java puts a lot of emphasis on early checking for possible problems, later dynamic

(runtime) checking, and eliminating situations that are error-prone. . . . The single

biggest difference between Java and C/C++ is that Java has a pointer model that elim-

inates the possibility of overwriting memory and corrupting data.

This feature is also very useful. The Java compiler detects many problems that, in other

languages, would show up only at runtime. As for the second point, anyone who has

spent hours chasing memory corruption caused by a pointer bug will be very happy

with this feature of Java.

If you are coming from a language like Visual Basic that doesn’t explicitly use pointers,

you are probably wondering why this is so important. C programmers are not so lucky.

They need pointers to access strings, arrays, objects, and even files. In Visual Basic, you

do not use pointers for any of these entities, nor do you need to worry about memory

allocation for them. On the other hand, many data structures are difficult to implement

in a pointerless language. Java gives you the best of both worlds. You do not need point-

ers for everyday constructs like strings and arrays. You have the power of pointers if

you need it, for example, for linked lists. And you always have complete safety, because

you can never access a bad pointer, make memory allocation errors, or have to protect

against memory leaking away.

Chapter 1. An Introduction to Java

The Java “White Paper” Buzzwords

Secure

Java is intended to be used in networked/distributed environments. Toward that

end, a lot of emphasis has been placed on security. Java enables the construction of

virus-free, tamper-free systems.

In the first edition of Core Java we said: “Well, one should ‘never say never again,’” and

we turned out to be right. Not long after the first version of the Java Development Kit

was shipped, a group of security experts at Princeton University found subtle bugs in

the security features of Java 1.0. Sun Microsystems has encouraged research into Java

security, making publicly available the specification and implementation of the virtual

machine and the security libraries. They have fixed all known security bugs quickly. In

any case, Java makes it extremely difficult to outwit its security mechanisms. The bugs

found so far have been very technical and few in number.

From the beginning, Java was designed to make certain kinds of attacks impossible,

among them:

• Overrunning the runtime stack—a common attack of worms and viruses

• Corrupting memory outside its own process space

• Reading or writing files without permission

A number of security features have been added to Java over time. Since version 1.1, Java

has the notion of digitally signed classes (see Volume II). With a signed class, you can be

sure who wrote it. Any time you trust the author of the class, the class can be allowed

more privileges on your machine.

NOTE: A competing code delivery mechanism from Microsoft based on its ActiveX technol-

ogy relies on digital signatures alone for security. Clearly this is not sufficient—as any user

of Microsoft’s own products can confirm, programs from well-known vendors do crash and

create damage. Java has a far stronger security model than that of ActiveX because it con-

trols the application as it runs and stops it from wreaking havoc.

Architecture Neutral

The compiler generates an architecture-neutral object file format—the compiled

code is executable on many processors, given the presence of the Java runtime sys-

tem. The Java compiler does this by generating bytecode instructions which have

nothing to do with a particular computer architecture. Rather, they are designed to

be both easy to interpret on any machine and easily translated into native machine

code on the fly.

This is not a new idea. More than 30 years ago, both Niklaus Wirth’s original implemen-

tation of Pascal and the UCSD Pascal system used the same technique.

Of course, interpreting bytecodes is necessarily slower than running machine instruc-

tions at full speed, so it isn’t clear that this is even a good idea. However, virtual

machines have the option of translating the most frequently executed bytecode

sequences into machine code, a process called just-in-time compilation. This strategy

has proven so effective that even Microsoft’s .NET platform relies on a virtual machine.

Chapter 1. An Introduction to Java

Chapter 1

■

An Introduction to Java

The virtual machine has other advantages. It increases security because the virtual

machine can check the behavior of instruction sequences. Some programs even produce

bytecodes on the fly, dynamically enhancing the capabilities of a running program.

Portable

Unlike C and C++, there are no “implementation-dependent” aspects of the specifi-

cation. The sizes of the primitive data types are specified, as is the behavior of arith-

metic on them.

For example, an

int

in Java is always a 32-bit integer. In C/C++,

int

can mean a 16-bit

integer, a 32-bit integer, or any other size that the compiler vendor likes. The only

restriction is that the

int

type must have at least as many bytes as a

short int

and cannot

have more bytes than a

long int

. Having a fixed size for number types eliminates a major

porting headache. Binary data is stored and transmitted in a fixed format, eliminating

confusion about byte ordering. Strings are saved in a standard Unicode format.

The libraries that are a part of the system define portable interfaces. For example,

there is an abstract Window class and implementations of it for UNIX, Windows,

and the Macintosh.

As anyone who has ever tried knows, it is an effort of heroic proportions to write a pro-

gram that looks good on Windows, the Macintosh, and ten flavors of UNIX. Java 1.0

made the heroic effort, delivering a simple toolkit that mapped common user interface

elements to a number of platforms. Unfortunately, the result was a library that, with a

lot of work, could give barely acceptable results on different systems. (And there were

often different bugs on the different platform graphics implementations.) But it was a

start. There are many applications in which portability is more important than user

interface slickness, and these applications did benefit from early versions of Java. By

now, the user interface toolkit has been completely rewritten so that it no longer relies

on the host user interface. The result is far more consistent and, we think, more attrac-

tive than in earlier versions of Java.

Interpreted

The Java interpreter can execute Java bytecodes directly on any machine to which

the interpreter has been ported. Since linking is a more incremental and lightweight

process, the development process can be much more rapid and exploratory.

Incremental linking has advantages, but its benefit for the development process is

clearly overstated. Early Java development tools were, in fact, quite slow. Today, the

bytecodes are translated into machine code by the just-in-time compiler.

High Performance

While the performance of interpreted bytecodes is usually more than adequate,

there are situations where higher performance is required. The bytecodes can be

translated on the fly (at runtime) into machine code for the particular CPU the

application is running on.

In the early years of Java, many users disagreed with the statement that the perfor-

mance was “more than adequate.” Today, however, the just-in-time compilers have

become so good that they are competitive with traditional compilers and, in some cases,

even outperform them because they have more information available. For example, a

just-in-time compiler can monitor which code is executed frequently and optimize just

Chapter 1. An Introduction to Java

剩余824页未读，继续阅读

mylajitong

粉丝: 0
资源: 6

Core Java 8th Vol I: 入门指南

Core Java Vol I 8th

core java 8th

Core Java 8th Ed. Volume I&II

Core Java. 8th Edition I

core java 8th edition, volume 2

Core Java 8th Edition Volume Two English Version

core java volume I 8th

Core Java Volume I 8th

Java 核心技术 英文版 第8版 上下两册 (Core Java 8th Edition) -- part1

Java 核心技术 英文版 第8版 上下两册 (Core Java 8th Edition) -- part2

最新资源

Java 核心技术英文版第8版上下两册 (Core Java 8th Edition) -- part1

Java 核心技术英文版第8版上下两册 (Core Java 8th Edition) -- part2