The Java language is an object-oriented programming language created by James Gosling and other engineers at Sun Microsystems. It was developed in 1991, as part of the Green Project, and officially announced on May 23, 1995, at SunWorld; being released in November. Gosling and friends initially designed Java, which was called Oak at first (in honour of a tree outside Gosling's office), to replace C++ (although the feature set better resembles that of Objective C). More on the history of Java can be found in the article about the Java platform, which includes the language, the Java virtual machine, and the Java API. Sun controls the Java specification and holds a trademark on the Java name.
There were four primary goals in the creation of the Java language:
The first characteristic, object orientation ("OO"), refers to a method of programming and language design. The main idea of OO is to design software around the "things" (ie. objects) it manipulates, rather than the actions it performs. This is based on the notion that the former change less frequently and radically than the latter, making such objects (actually the entities containing data) the more stable foundation for a software system's design. The intent is to make large software projects easier to manage, thus improving quality and reducing the number of failed projects.
The second characteristic, platform independence, means that programss written in the Java language must run similarly on diverse hardware. One should be able to write a program once and run it anywhere. This is achieved by compiling Java language code "halfway" to bytecode--simplified machine instructions that conform to a set standard. The code is then run on a virtual machine, a program written in native code on the host hardware that translates generic Java bytecode into usable code on the hardware. Further, standardized libraries are provided to allow access to features of the host machines (such as graphics and networking) in unified ways. The Java language also includes support for multi-threaded programs--a necessity for many networking applications.
The first implementations of the language used an interpreted virtual machine to achieve portability, and many implementations still do. These implementations produce programs that run more slowly than the fully-compiled programs created by the typical C++ compiler and some later Java language compilers, so the language suffered a reputation for producing slow programs. More recent implementations of the Java VM produce programs that run much faster, using multiple techniques.
The first of these is to simply compile directly into native code like a more traditional compiler, skipping bytecodes entirely. This achieves great performance, but at the expense of portability. Another technique, the just-in-time compiler or "JIT", compiles the Java bytecodes into native code at the time the program is run. More sophisticated VMs even use dynamic recompilation, in which the VM can analyze the behavior of the running program and selectively recompile and optimize critical parts of the program. Both of these techniques allow the program to take advantage of the speed of native code without losing portability.
Portability is a technically difficult goal to achieve, and Java's success at that goal is a matter of some controversy. Although it is indeed possible to write programs for the Java platform that behave consistently across many host platforms, the large number of available platforms with small errors or inconsistencies led some to parody Sun's "Write once, run anywhere" slogan as "Write once, debug everywhere".
Platform independent Java is, however, very successful with server side applications, such as web services, servlets, or Enterprise Java Beans.
The Java platform was one of the first systems to provide wide support for the execution of code from remote sources. An applet could run within a user's browser, executing code downloaded from a remote HTTP server. The remote code runs in a highly restricted "sandbox", which protects the user from misbehaving or malicious code; publishers could apply for a certificate that they could use to digitally sign applets as "safe", giving them permission to break out of the sandbox and access the local filesystem and network, presumably under user control.
Most generally consider Java technology to deliver reasonably well on all
these promises. The language is not, however, without drawbacks.
Java tends to be more high-level than similar languages (such as C++), which means that the Java language lacks features such as hardware-specific data types and low-level pointers to arbitrary memory. Although these features are frequently abused or misused by programmers, they are also powerful tools. However, the Java Native Interface (JNI) does provide a way for a Java program to call non-Java code in order to leverage the capabilities of other languages when necessary.
Some also see a shortcoming in its lack of multiple inheritance, a powerful feature of several object-oriented languages such as C++, Eiffel, and CLOS. Java subclasses have only one chance to inherit implementation by choosing one superclass, which can lead to false dilemas (should HouseBoat inherit House or Boat?) and rules out certain implementation techniques such as mixins. However, proponents believe Java's multiple inheritence of interfaces is a good trade-off, providing most of the benefits of full multiple inheritence while sidestepping thorny situations in which a class inherits multiple conflicting implementations.
Java's paradigm of bytecode interpretation is widely seen to provide portability only at the expense of performance degradation relative to native code. Dynamic compilation helps tremendously, but still typically cannot beat statically-compiled code; this is because compilation occurs at run-time, and thus counts against the performance of the program, causing dynamic compilers to apply optimizations sparingly. However, precisely because dynamic compilers are present at runtime, they can take advantage of dynamic program behaviour, and can even recompile portions of the program as conditions change. Therefore, dynamic compilers can perform optimizations that static compilers cannot; and there do exist some programs for which dynamically-compiled code is faster than statically-compiled. (For instance, long-running programs whose behaviour depends on input data may fall into this category.) It is not unreasonable to suppose that this set of programs will grow as dynamic compilation technology improves.
Java's heavy use of heap-allocated objects causes programs to consume more memory than similar programs written in lower-level languages, where data storage can be optimized at a fine granularity. Because it treats almost everything is an object, Java encourages a style in which objects contain a lot of references to other objects rather than raw data, making the objects larger and the data less localized. Both of these effects tend to work against modern memory hierarchies, whose caching schemes thrive on small working sets and good locality.
There are some who believe that for certain projects, object orientation makes work harder instead of easier. This particular complaint is not unique to the Java language but applies to other object-oriented languages as well.
An example of a hello world program in the Java language follows:
Java does not have goto statements, as their use is widely considered poor programming practice. There are, however, some uses for goto that are considered acceptable, and Java have facilities to duplicate such functionality. Note that goto is a reserved word and as such cannot be used for identifiers.
Java provides two statements to exit from a loop in the midst of an iteration. The statement
Java's break and continue statements are more powerful than the C and C++ constructs of the same name, in that they are capable of exiting more than one loop-nesting level. Specifically, to jump out of a particular loop, one can label the loop, and then affix the label to the break or continue statement. To achieve similar functionality in C and C++ would require the use of a goto statement.
For instance:
Overview
Object orientation
Platform independence
Secure execution of remote code
Evaluation
Language
public class HelloWorld {
public static void main(String[] args) {
System.out.println("Hello world!");
}
}
Control structures
Loops
while (Boolean expression) {
statement(s)
}
do {
statement(s)
} while (Boolean expression);
for (initialisation ; termination condition ; incrementing expr) {
statement(s)
}
Conditional statements
if (Boolean expression) {
statement(s)
}
if (Boolean expression) {
statement(s)
} else {
statement(s)
}
With else if arbitrarily complex if-then-constructions may be built.if (Boolean expression) {
statement(s)
} else if (Boolean expression) {
statement(s)
} else if (Boolean expression) {
statement(s)
} else {
statement(s)
}switch (integer expression) {
case constant integer expr:
statement(s)
break;
...
default:
statement(s)
break;
}
Exception handling
try {
statement(s)
} catch (exception type) {
statement(s)
} catch (exception type) {
statement(s)
} finally {
statement(s)
}
Unstructured control flow
Early exit from loops
continue;
terminates the current iteration of a loop and starts the next one, behaving as a goto jumping to the top of the loop body. Similarly, the statement
break;
exits the loop, terminating the current iteration and executing no more iterations. The effect is that of a goto jumping just past the end of the loop.outer: while (true) {
inner: while (true) {
break; // Exits the innermost loop
break inner; // Also exits the innermost loop
break outer; // Exits the outermost loop
}
}This should not be confused with the
break label;
and
continue label;
statements in C and C++, which function identically to goto.
| Variable Type | Description |
|---|---|
| byte | 8-bit signed (two's complement) integer |
| short | 16-bit signed (two's complement) integer |
| int | 32-bit signed (two's complement) integer |
| long | 64-bit signed (two's complement) integer |
| float | 32-bit single-precision floating point (IEEE 754 standard) |
| double | 64-bit double-precision floating point
(IEEE 754 standard) |
| char | 16-bit single Unicode character |
| boolean | true or false |
Characters use the 16-bit Unicode encoding. It contains all of the usual characters, but also includes character sets for many languages other than English, including Greek, Cyrillic, Chinese, Arabic, etc. Java programs can use all of these characters, although most editors do not have built-in support for character sets other than the usual ASCII characters. Arrays and strings are not primitive types: they are objects.
The language as such has been stable since JDK 1.0, except for the addition of the assert keyword in 1.4; the class libraries that come with the JDK got larger and have changed in some parts. Extensionss and architectures closely tied to the Java programming language include: J2EE, J2ME, JNDI, JSML, JDBC, JAIN, JDMK, Jini, Jiro, JXTA, JavaSpaces, JMI.
1.5 (codename Tiger) is scheduled to be released in the June-August timeframe of 2004. Major changes include:
There is an interpreted version of Java called beanshell which may be used as a shell scripting language.
The interpreter may be embedded in a Java application to make it scriptable.
Versions
Java was initially released as the Java Development Kit 1.0 (JDK 1.0). This included the Java runtime (the virtual machine and the class libraries), and the development tools (e.g. the Javac compiler). Later, Sun also provided a runtime-only package, called the Java Runtime Environment (JRE). The first name stuck, however, so usually people refer to a particular version of Java by its JDK version (e.g. JDK 1.4). The JDKs of version 1.2 and later versions are often called Java 2 as well. For example, the official name of JDK 1.4 is The Java(TM) 2 Platform, Standard Edition version 1.4.
(from [1])
Interpreted version
See also
External links
