Am 03.03.2014 13:44, schrieb John Cowan:
On Sun, Mar 2, 2014 at 3:54 PM, Per Bothner <p...@bothner.com <mailto:p...@bothner.com>> wrote: The "standard" solution I believe is to compile A twice: first with a "stub compiler" that ignores "module internals". This generates a skeletal A.class that can be read by javac. After B is compiled by javac, then we compile A for real to generate the real A.class. Another approach is to have a mode of the L1 compiler that generates Java rather than bytecode, and then let javac deal with it all, since it already understands this problem.
But that works with even less languages bye Jochen -- Jochen "blackdrag" Theodorou - Groovy Project Tech Lead blog: http://blackdragsview.blogspot.com/ german groovy discussion newsgroup: de.comp.lang.misc For Groovy programming sources visit http://groovy-lang.org -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To unsubscribe from this group and stop receiving emails from it, send an email to jvm-languages+unsubscr...@googlegroups.com. To post to this group, send email to jvm-languages@googlegroups.com. Visit this group at http://groups.google.com/group/jvm-languages. For more options, visit https://groups.google.com/groups/opt_out.
