On Mon, Dec 21, 2009 at 9:21 AM, Charles Oliver Nutter <[email protected]> wrote: > On Sun, Dec 20, 2009 at 8:28 PM, Per Bothner <[email protected]> wrote: >> The problem is picking a representation. A .class file is one valid >> well-understood representation. An API might be better, but designing >> one for multiple languages is probably not feasible. (Remember CORBA.) >> >> I think the best choice for an API may be javax.lang.model.*. >> It very Java-centric, but that's probably the best we can do. >> It has the big advantage that javac already implements it. > > I was actually thinking along the lines of the mirror API that the > Annotation Processing Tool uses: > > http://java.sun.com/j2se/1.5.0/docs/guide/apt/mirror/overview-summary.html > > Again, I may be naïve but it seems to me we could easily form a common > mirror type system that we'd feed to the orchestration logic. Starting > with the mirror API would be pretty easy, since it's basically *all* > interfaces.
I like the sound of this ... good choice :-) 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.
