John Rose a écrit : > The mlvm/langtools patch repository has support for some small Java > extensions, which I am in the process of proposing to the Java > language people. > > I have wired the updated javac into the ant scripts that NetBeans > uses, and can build invokedynamic call sites directly from Java code > in the NetBeans editor. This will be a preferred way to create call > sites for metaobject protocol infrastructure and any parts of dynamic > language runtimes written in Java. (Dynamic languages will probably > not compile via Java, but use ASM to generate invokedynamic calls > directly.) You'll see the tweaks for that on my next hotspot push. > > Meanwhile, NetBeans still (very reasonably) reports the extensions as > syntax or type errors. I just filed a NetBeans RFE to get this > fixed. Now all we need is a NetBeans expert! (Are *you* that > expert? :-) > > http://www.netbeans.org/issues/show_bug.cgi?id=157264 > > Best wishes, > -- John > John, I am not a big fan of the exotic identifier proposal mostly because i doesn't understand the need and because using '#' creates conflicts with several closure proposal (BGGA and CICE) and my modest property proposal.
Correct me if i'm wrong, you need exotic identifiers if you are a language developer that want to implement a part of the langage runtime in Java. But if you are a language developer, you control the compiler of that language so you can lookup for extra meta-data when you want to call a method, a field or a class written in Java. By example, these metadata can be implemented using annotations with no problem. cheers, Rémi _______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
