sokoot
شنبه 30 اردیبهشت 1385, 08:00 صبح
Sun Microsystems, present on Java futures and Dolphin (http://webcast-west.sun.com/ramgen/archives/06D00627/06D00627_16_300.rm)
There were two points that Graham wanted to be clear on. They wanted to be very cautious about changing the language. Though they have had many interesting suggestions, they needed to be cautious in how they changed the language.
We want better performance, not going to give up on stability, robustness, compatibility, and push to improve on monitoring and management.One of the features currently not on the table is operator overloading. This controversial feature may offer benefits but are these benefits worth the risk? Though Graham was polite about the subject it was clear that he didn’t think so.
So just what is on the table? The first item up for discussion was XML literals. The follow code was taken from an supporting slide.
XML speaker = <who> { mark } </who>;
XML talk = <session> { speaker }
<title> { “XML in Java” } </title>
<when> { “Wednesday 1:30pm” } </when>
</session>;
Included in the talk was a discussion of super packages. A super package is a different way to organize your application. It is being designed with support for large application in mind. In particular, super package should fill requirements that currently cannot be meet with the Java ARchive (JAR) standard. That requirement is to provide extra package level scoping that will allow one to hide all the API classes for a particular module. API classes will need to be explicity named before one can use them from another module. There will also be support for versioning and dependency mappings. Super packages will be supported both in language and runtime.
Other features included;
a new byte code to support the invocation of methods in dynamic languages
lightweight method references for GUI event handlers
Bean bindings
More Java2D expect more hardware acceleration
Better support for scripting languages
Beanshell seems like a good candidate to be included into DolphinOther languages to be supported are VisualBasic and JavaScript in the web tier. It is expected that you will be able to write a Servlet in JavaScript. However don’t expect to be running your VB application in the JVM anytime soon. While support will exist, the support will not clone the windows platform. However you will be able to call VB from Java and Java from VB.
The next question is, when will we be seeing a JSR in the JCP to cover all of this activity?
There were two points that Graham wanted to be clear on. They wanted to be very cautious about changing the language. Though they have had many interesting suggestions, they needed to be cautious in how they changed the language.
We want better performance, not going to give up on stability, robustness, compatibility, and push to improve on monitoring and management.One of the features currently not on the table is operator overloading. This controversial feature may offer benefits but are these benefits worth the risk? Though Graham was polite about the subject it was clear that he didn’t think so.
So just what is on the table? The first item up for discussion was XML literals. The follow code was taken from an supporting slide.
XML speaker = <who> { mark } </who>;
XML talk = <session> { speaker }
<title> { “XML in Java” } </title>
<when> { “Wednesday 1:30pm” } </when>
</session>;
Included in the talk was a discussion of super packages. A super package is a different way to organize your application. It is being designed with support for large application in mind. In particular, super package should fill requirements that currently cannot be meet with the Java ARchive (JAR) standard. That requirement is to provide extra package level scoping that will allow one to hide all the API classes for a particular module. API classes will need to be explicity named before one can use them from another module. There will also be support for versioning and dependency mappings. Super packages will be supported both in language and runtime.
Other features included;
a new byte code to support the invocation of methods in dynamic languages
lightweight method references for GUI event handlers
Bean bindings
More Java2D expect more hardware acceleration
Better support for scripting languages
Beanshell seems like a good candidate to be included into DolphinOther languages to be supported are VisualBasic and JavaScript in the web tier. It is expected that you will be able to write a Servlet in JavaScript. However don’t expect to be running your VB application in the JVM anytime soon. While support will exist, the support will not clone the windows platform. However you will be able to call VB from Java and Java from VB.
The next question is, when will we be seeing a JSR in the JCP to cover all of this activity?