lambda and dynamic JVM languages interropt

[Remi Forax]

There is a blog post from Jim Connors about a dynamic language developed 
by GE and ported to the JVM
(see the message below).
One of the item of the blog post is that JVM languages can benefit from 
the Java integration and leverage features like lambdas.

Thinking a bit about that, the current lambda metafactory API is not 
totally aligned with this goal.
The current API offers only single entry point (two in fact with 
serialization) so there is no way for
JVM language developers to choose which representation of lambdas is 
most suited for their language
(dynamic generation of inner-classes or method handle proxy).
I think we should provide 3 entry points (6 with serialization), the one 
Java uses which select the best implementation
and delegates to one of the lambda implementation entrypoints, and 2 for 
the two ways to represent a lambda.

cheers,
Rémi

-------- Original Message --------
Subject: 	nice blog post on Majik
Date: 	Mon, 5 Nov 2012 16:44:30 -0800
From: 	John Rose <john.r.rose at oracle.com>
Reply-To: 	Da Vinci Machine Project <mlvm-dev at openjdk.java.net>
To: 	Da Vinci Machine Project <mlvm-dev at openjdk.java.net>



Some of you may remember reading posts from Duncan MacGregor or seeing the talk on GE's Majik system at this year's JVM Language Summit.

There's a new Oracle blog entry on their work here:

https://blogs.oracle.com/jtc/entry/sprinkle_some_magik_on_that

It includes a rehearsal of business reasons to move from a proprietary VM to the JVM.

Enjoy!

— John
_______________________________________________
mlvm-dev mailing list
mlvm-dev at openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev