April 2002 Draft
Tuesday, October 9, 2001
The proposed features are derived from the goals above. Consider, for example, the goals of writing modular and robust applications.
To make packages work we need to make the language more robust in other areas as well. It would not be good if one package
Object.toString or added methods to the
Array prototype and thereby corrupted another
package. We can simplify the language by eliminating many idioms like these (except when running legacy programs, which would
not use packages) and provide better alternatives instead. This has the added advantage of speeding up the language’s implementation
by eliminating thread synchronization points. Making the standard packages robust can also significantly reduce the memory
requirements and improve speed on servers by allowing packages to be shared among many different requests rather than having
to start with a clean set of packages for each request because some other request might have modified some property.
1.5 lacks support for integers, making it hard to interface with a Java method that expects a
Last modified Tuesday, October 9, 2001