Errata for
The Java^TM Virtual Machine Specification,

If you find an error in the book, please check this list first to see if it is already known. If not, please mail us the relevant information, including page numbers. All errata will be fixed in the next possible printing.

This page contains all the technical errata in the book -- those things that are wrong or lead you astray. If you have found a minor error, such as a typo or grammatical error, please check the minor errors list before you email us about it.

Preface

Introduction

Java^TM Concepts

Structure of the Java Virtual Machine

The class File Format

Page 99

The long hexadecimal constants given in the first two bullet items are incorrect.

• If the argument is 0x7ff0000000000000, the double value will be positive infinity.
• If the argument is 0xfff0000000000000, the double value will be negative infinity.

[1/8/96]

Page 100

The first picture in Section 4.4.7 should have "bits 0-6" in the box, rather than "bits 0-7". [11/22/96]

Page 109

The first paragraph of section 4.7.3 is slightly misleading. If a static field has a ConstantValue attribute, then its meaning is as indicated. If a non-static field has a ConstantValue attribute, then the attribute is silently ignored. [4/18/97]

Constant Pool Resolution

Java Virtual Machine Instruction Set

Page 158

There should be a third "square bullet" under the first-level bullet labeled "If S is an array type." The square bullet should say:

If T is an interface type, then T must be the interface Cloneable.

[4/25/97]

Page 175

The error on page 158 (see above) is repeated here. [2/20/97, 4/25/97]

Page 257

The error on page 158 (see above) is repeated here. [2/20/97, 4/25/97]

Compiling for the Java Virtual Machine

Threads and Locks

An Optimization

Page 409

The sentence "The operands of the invokespecial instruction are not modified." should be deleted. The operands are modified, as is described in the instruction definition. [3/24/97]

Opcode Mnemonics by Opcode

Index