You manipulate objects with references
2. The stack. This lives in the general random-access memory (RAM) area, but has direct support from the processor via its stack pointer. The stack pointer is moved down to create new memory and moved up to release that memory. This is an extremely fast and efficient way to allocate storage, second only to registers. The Java system must know, while it is creating the program, the exact lifetime of all the items that are stored on the stack. This constraint places limits on the flexibility of your programs, so while some Java storage exists on the stack—in particular, object
references—Java objects themselves are not placed on the stack .
You must create all the objects
Where storage lives
There are five different places to store data:
1.
Registers. This is the fastest storage because it exists in a place different from that of other storage: inside the processor. However, the number of registers is severely limited, so registers are allocated as they are needed. You don’t have direct control, nor do you see any evidence in your programs that registers even exist (C & C++, on the other hand, allow you to suggest register allocation to the compiler).
2. The stack. This lives in the general random-access memory (RAM) area, but has direct support from the processor via its stack pointer. The stack pointer is moved down to create new memory and moved up to release that memory. This is an extremely fast and efficient way to allocate storage, second only to registers. The Java system must know, while it is creating the program, the exact lifetime of all the items that are stored on the stack. This constraint places limits on the flexibility of your programs, so while some Java storage exists on the stack—in particular, object
references—Java objects themselves are not placed on the stack .
3.
The heap. This is a general-purpose pool of memory (also in the RAM area) where all Java objects live. The nice thing about the heap is that, unlike the stack, the compiler doesn’t need to know how long that storage must stay on the heap. Thus, there’s a great deal of flexibility in using storage on the heap. Whenever you need an object, you simply write the code to create it by using
new, and the storage is allocated on the heap when that code is executed. Of course there’s a price you pay for this flexibility: It may take more time to allocate and clean up heap storage than stack storage (if you even could create objects on the stack in Java, as you can in C++).
4. Constant storage. Constant values are often placed directly in the program code, which is safe since they can never change. Sometimes constants are cordoned off by themselves so that they can be optionally placed in read-only memory (ROM), in embedded systems.
5. Non-RAM storage. If data lives completely outside a program, it can exist while the program is not running, outside the control of the program. The two primary examples of this are streamed objects, in which objects are turned into streams of bytes, generally to be sent to another machine, and persistent objects, in which the objects are placed on disk so they will hold their state even when the program is terminated. The trick with these types of storage is turning the objects into something that can exist on the other medium, and yet can be resurrected into a regular RAM-
based object when necessary. Java provides support for lightweight persistence, and mechanisms such as JDBC and Hibernate provide more sophisticated support for storing and retrieving object information in databases.
4. Constant storage. Constant values are often placed directly in the program code, which is safe since they can never change. Sometimes constants are cordoned off by themselves so that they can be optionally placed in read-only memory (ROM), in embedded systems.
5. Non-RAM storage. If data lives completely outside a program, it can exist while the program is not running, outside the control of the program. The two primary examples of this are streamed objects, in which objects are turned into streams of bytes, generally to be sent to another machine, and persistent objects, in which the objects are placed on disk so they will hold their state even when the program is terminated. The trick with these types of storage is turning the objects into something that can exist on the other medium, and yet can be resurrected into a regular RAM-
based object when necessary. Java provides support for lightweight persistence, and mechanisms such as JDBC and Hibernate provide more sophisticated support for storing and retrieving object information in databases.
Special case: primitive types
Primitive type | Size | Minimum | Maximum | Wrapper type |
boolean | — | — | — | Boolean |
char | 16 bits | Unicode 0 | Unicode 2^16-1 | Character |
byte | 8 bits | -128 | +127 | Byte |
short | 16 bits | -2^15 | +2^15-1 | Short |
int | 32 bits | -2^31 | +2^31-1 | Integer |
long | 64 bits | -2^63 | +2^63 | Long |
float | 32 bits | IEEE754 | IEEE754 | Float |
double | 64 bits | IEEE754 | IEEE754 | Double |
void | — | — | — | Void |
All numeric types are signed, so don’t look for unsigned types.
The size of the
boolean
type is not explicitly specified; it is only defined to be able to take
the literal values true or false .
the literal values true or false .
High-precision numbers
BigInteger supports arbitrary-precision integers. This means that you can accurately represent integral values of any size without losing any information during operations.
BigDecimal is for arbitrary-precision fixed-point numbers; you can use these for accurate monetary calculations, for example.
BigDecimal is for arbitrary-precision fixed-point numbers; you can use these for accurate monetary calculations, for example.
Arrays in Java
When you create an array of objects, you are really creating an array of references, and each
of those references is automatically initialized to a special value with its own keyword: null. When Java sees null, it recognizes that the reference in question isn’t pointing to an object. You must assign an object to each reference before you use it, and if you try to use a reference that’s still null, the problem will be reported at run time. Thus, typical array errors are prevented in Java.
You can also create an array of primitives. Again, the compiler guarantees initialization because it zeroe s the memory for that array.
of those references is automatically initialized to a special value with its own keyword: null. When Java sees null, it recognizes that the reference in question isn’t pointing to an object. You must assign an object to each reference before you use it, and if you try to use a reference that’s still null, the problem will be reported at run time. Thus, typical array errors are prevented in Java.
You can also create an array of primitives. Again, the compiler guarantees initialization because it zeroe s the memory for that array.
You never need to destroy an object
Thus the C and C++ ability to “hide” a variable in a larger scope is not allowed, because the Java designers thought that it led to confusing programs
Creating new data types: class
Default values for primitive members:
Primitive type | Default |
boolean | false |
char | '\u0000'(null) |
byte | (byte)0 |
short | (short)0 |
int | 0 |
long | 0L |
float | 0.0f |
double | 0.0d |
The default values are only what Java guarantees
when the variable is used as a member of a
class .
class .
在java中原始数据类型的变量若不为new出的对象,则在程序中必须初始化,否则会报错。
Methods, arguments, and return values
Building a Java program
The static keyword
You can achieve both of these effects with the
static keyword. When you say something is
static, it means that particular field or method is not tied to any particular object instance of
that class. So even if you’ve never created an object of that class you can call a static method
or access a static field.
static, it means that particular field or method is not tied to any particular object instance of
that class. So even if you’ve never created an object of that class you can call a static method
or access a static field.
Your first Java program
import java.util.*;
class StaticTest{
static int i = 47;
}
class Incrementable{
static int increment(){
return StaticTest.i++;
}
}
public class HelloData{
public static void main(String []args){
StaticTest st1 = new StaticTest();
StaticTest st2 = new StaticTest();
Incrementable sf = new Incrementable();
System.out.println(Incrementable.increment());
System.out.println(StaticTest.i++);
System.out.println(st1.i++);
System.out.println(StaticTest.i);
System.out.println(sf.increment());
System.out.println(Incrementable.increment());
System.out.println("Hello, it's: ");
System.out.println(new Date());
}
}
class StaticTest{
static int i = 47;
}
class Incrementable{
static int increment(){
return StaticTest.i++;
}
}
public class HelloData{
public static void main(String []args){
StaticTest st1 = new StaticTest();
StaticTest st2 = new StaticTest();
Incrementable sf = new Incrementable();
System.out.println(Incrementable.increment());
System.out.println(StaticTest.i++);
System.out.println(st1.i++);
System.out.println(StaticTest.i);
System.out.println(sf.increment());
System.out.println(Incrementable.increment());
System.out.println("Hello, it's: ");
System.out.println(new Date());
}
}
RESULT:
47
48
49
50
50
51
Hello, it's:
Tue Sep 24 15:26:16 CST 2013
48
49
50
50
51
Hello, it's:
Tue Sep 24 15:26:16 CST 2013
There’s a certain library of classes that are automatically brought into every Java file:
java.lang.
Comments and embedded documentation