Difference between revisions of "MOP and Invokedynamic"
From JVMLangSummit
Jump to navigationJump to search (New page: == MOP and Indy == Attila Szegedi ; Project: ; Blog: ; Slides: Image:file.pdf === Abstract === = Background = = Current Status = = Future = = Key Issues for Discussion = ''...) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== MOP and Indy == | == MOP and Indy == | ||
| − | Attila Szegedi | + | Attila Szegedi - Sourceforge.net |
; Project: | ; Project: | ||
; Blog: | ; Blog: | ||
| − | ; Slides: [[Image: | + | ; Slides: [[Image:Metaobject_Protocol_Meets_Invokedynamic.pdf]] |
=== Abstract === | === Abstract === | ||
| + | Metaobject Protocol Meets Invokedynamic — Attila Szegedi | ||
| + | |||
| + | Having a largely stabilized specification and working implementation of JSR-292 opened the way for a rethinking of the JVM Dynamic Languages Metaobject Protocol as a framework for runtime linking of invokedynamic calls between language runtimes. In this talk, I present the architecture of the framework in its current state: the pluggable linker mechanism, the type conversion subsystem, and the set of conventions that build on top of these two to implement a subset of well-known call identifiers that serve as the metaobject protocol nomenclature commonly understood by dynamic languages. | ||
= Background = | = Background = | ||
Latest revision as of 11:13, 17 September 2009
Contents
MOP and Indy
Attila Szegedi - Sourceforge.net
- Project
- Blog
- Slides
- File:Metaobject Protocol Meets Invokedynamic.pdf
Abstract
Metaobject Protocol Meets Invokedynamic — Attila Szegedi
Having a largely stabilized specification and working implementation of JSR-292 opened the way for a rethinking of the JVM Dynamic Languages Metaobject Protocol as a framework for runtime linking of invokedynamic calls between language runtimes. In this talk, I present the architecture of the framework in its current state: the pluggable linker mechanism, the type conversion subsystem, and the set of conventions that build on top of these two to implement a subset of well-known call identifiers that serve as the metaobject protocol nomenclature commonly understood by dynamic languages.
Background
Current Status
Future
Key Issues for Discussion
(please expand cooperatively)
