Thanks! Still working through it, but a fundamental question: Why does invokedynamic mirror invokevirtual, esp. in looking like an instance method call? Isn't a multi-language extension point like invokedynamic a good place to abandon the hard-wiring of single- dispatch? It seems like further dictation of Java-like object systems, at the expense of newer (and older) ideas, like languages based on functions, or non-member dispatch methods.
It's all function calls underneath. Distinguishing a 'receiver' makes the first argument needlessly special - in particular, it can't be null or a primitive. The method handles seem to get this right, why shouldn't invokedynamic do the same? Rich On May 20, 12:17 am, John Rose <[EMAIL PROTECTED]> wrote: > Hello, JVM language folks! > > The early draft review for the invokedynamic instruction is now > available. You can find more information via my blog: > http://blogs.sun.com/jrose/entry/invokedynamic_goes_public > > Best wishes, > -- John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
