Monday, May 17, 2010

Java 1.5 - New Features over Java 1.4

Java Language Features

This long-awaited enhancement to the type system allows a type or method to operate on objects of various types while providing compile-time type safety. It adds compile-time type safety to the Collections Framework and eliminates the drudgery of casting.
eg: HashSet<String>

Enhanced for Loop (for-each)
This new language construct eliminates the drudgery and error-proneness of iterators and index variables when iterating over collections and arrays.
eg: for (Rank rank : ranks)

This facility eliminates the drudgery of manual conversion between primitive types (such as int) and wrapper types (such as Integer).
eg: int i =1; Integer iWrapped = i;

Typesafe Enums
This flexible object-oriented enumerated type facility allows you to create enumerated types with arbitrary methods and fields. It provides all the benefits of the Typesafe Enum pattern without the verbosity and the error-proneness.
eg: enum Season { WINTER, SPRING, SUMMER, FALL }

This facility eliminates the need for manually boxing up argument lists into an array when invoking methods that accept variable-length argument lists.
eg: String result = MessageFormat.format( "At {1,time} on {1,date}, there was {2} on planet " + "{0,number,integer}.", 7, new Date(), "a disturbance in the Force");

Static Import
This facility lets you avoid qualifying static members with class names without the shortcomings of the "Constant Interface antipattern."
eg: import static java.lang.Math.PI;

Metadata (Annotations)
This language feature lets you avoid writing boilerplate code under many circumstances by enabling tools to generate it from annotations in the source code. This leads to a "declarative" programming style where the programmer says what should be done and tools emit the code to do it. Also it eliminates the need for maintaining "side files" that must be kept up to date with changes in source files. Instead the information can be maintained in the source file.
eg: In annotations with a single element, the element should be named value, as shown below:
 * Associates a copyright notice with the annotated API element.
public @interface Copyright {
    String value();
It is permissible to omit the element name and equals sign (=) in a single-element annotation whose element name is value, as shown below:
@Copyright("2002 Yoyodyne Propulsion Systems")
public class OscillationOverthruster { ... }

J2SE 5.0 - new features
Performance Improvements

No comments:

Post a Comment