On Thu, Dec 17, 2009 at 10:56 AM, Matt Fowles <[email protected]> wrote: > Charlie~ > Also worth considering is the runtime/dev time aspects of such a system. It > would be nice to have some amount of infrastructure common so not every > language needs to implement a full set of Eclipse/InteliJ plugins from > scratch. > The two should almost certainly be separate projects, but it would be nice > if the joint compiler had enough hooks that IDE's could use them.
Yes, absolutely! I may be naive, but what we really want here is simply a set of common protocols for doing the following: * Requesting from a language what types and methods are provided by a set of source files * Providing to a language services to look up types from other languages * Resolution and error handling when no languages provide a type or multiple languages incompatibly provide the same type * Eventually generating the dumb bytecode once all participating languages have satisfied their type dependencies Given this, IDE support would be a natural extension. And it's important to point out that "common compiler infrastructure" has nothing to do with code generation...it's just a type-wrangler that says "yes, I have that type" or "no, I don't have that type" and then triggers all the language-specific bits to eventually cough up their bytecode. That can't really be hard, can it? - 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.
