For the purpose of getting a discussion going, I'm posting the list
from the blog. However, people should still check out the post and
join the observer list :-).

#  We are making significant changes to the JVM instruction architecture.

# The occasion for this is a crop of new dynamic languages. There are
business reasons for the JVM to support these languages.

# Liz Kiener of the JCP.org PMO introduced us to the Java Community
Process (JCP).

# EG consensus: We want public review early. This means producing an
EDR (early draft review required by JCP).

# To make the current Proof of Concept design public, we need to pass
the "red face test". That is, the design shows a direction that we as
an EG think is worth explaining and improving. Since this is not a
voting milestone, the EDR spec. can be incomplete and have unresolved
issues.

# The original JSR 292 language includes not only invokedynamic but
also some sort of class modification or extension. Based on recent
experience, what's needed beyond invokedynamic is probably some sort
of lightweight behavioral extension (method handles, autonomous
methods, etc.). Further discussion is required.

# An OpenJDK open source sub-project is going to help create the RI
(reference implementation required by JCP) for JSR 292.

# This project (the MLVM) is likely to include other changes, and it
is up to our EG which changes we think are ready to standardize and
which to push off to MR (maint. rel.) or another JSR.

# We should use [email protected] as a sort of early
comment source, to help us shape our work.

# We will continue to work on EDR readiness and meet again soon

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to