Le 14/07/2010 06:34, Per Bothner a écrit :
On 07/14/2010 12:30 AM, Dibyendu Majumdar wrote:
- Similar to Go but not exactly the same - no point adding a feature
that cannot be done efficiently in the JVM. Therefore closures only
when natively supported in JVM (i.e. 7).
Kawa implemented closures efficiently using JDK 1.1.
Lots of languages implement closures - no need to worry
about the efficiency of closures. Of course JDK 7 closures
can make closures simpler to implement and/or more efficient.
For example calling an unknown closure takes takes or returns
a primitive value requires boxing, but that's not that common,
and it could also be optimized by the JVM.
I've backported java.dyn.* API to 1.5/1.6 VM.
See http://code.google.com/p/jvm-language-runtime/
The yet to appear release introduces an offline weaver.
I've planned to release it during the JVM Summit :)
Rémi
--
You received this message because you are subscribed to the Google Groups "JVM
Languages" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jvm-languages?hl=en.
