On Thu, Dec 17, 2009 at 4:56 PM, Matt Fowles <[email protected]> wrote: > 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. > Matt
I'm not so sure about this. There is definitely a benefit to sharing infrastructure between IDEs *for a given language* (eg. there is a fair amount of sharing between the Scala tooling for Eclipse, Netbeans and IDEA), but I don't think this carries over to multiple languages in a way that Charlie's kind of proposal can address. That's because the bulk of that sharing would overlap with the IDE's own frameworks at one end and collide with language differences at the other (ie. the most interesting tooling is very language specific). Here's an example. To enable cross language search and refactoring in Eclipse all participating languages need to hook into the JDT's indexer. Doing this is inescapably Eclipse-specific, and beyond the basic job of mapping non-Java language symbols into Java there's really nothing much to factor out which isn't either IDE-specific or language-specific. Cheers, Miles -- Miles Sabin tel: +44 (0)7813 944 528 skype: milessabin http://www.chuusai.com/ http://twitter.com/milessabin -- 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.
