Ok, I think it's time we formally got some of our compiler mavens together to create a common AOT compiler infrastructure we can all plug into. This was discussed briefly at JVM-L, but I'm not sure anything has come of it yet.
Right now I believe there are at least two separate efforts to build joint compilers: the Groovy efforts to joint compile Groovy+Java, Groovy+Scala, and Groovy+Java+Scala; and the Scala efforts to joint compile Scala+Java. Obviously we other JVM languages would like to join in the fun. The common infrastructure would be responsible for resolving methods (perhaps pluggable), getting lists of provided types and methods from languages (definitely pluggable), and providing needed types and methods to languages. Structurally, it seems like it wouldn't be difficult to do. I am now interested in this since this is essentially *all* JRuby would need to have a full ahead-of-time compiler that can produce normal Java classes, and it seems silly to either depend on Groovy/Scala joint compilers (our distribution is already too big) or to write this all completely from scratch. So what's the deal, folks? Anyone else interested in this? Can we cannibalize an existing compiler and make the type provision/requisition logic per-language-pluggable? - Charlie -- 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.
