On Mon, Jan 12, 2009 at 8:56 PM, Charles Oliver Nutter <[email protected]> wrote: > > Rodrigo B. de Oliveira wrote: >>> It meets several goals I've had for Duby, which would mean I >>> might not have to implement them :) >> >> Nice :) > > Boo also has (as I understand it) a very pluggable toolchain.
Yes. > My thought > has been that I could use Duby syntax but instead build a Boo AST and > then let it take over from there. > Yes. That's pretty much how UnityScript (the scripting language for Unity 3D) was implemented. > What sort of runtime dependencies does Boo have? The boo compiler framework was mostly implemented in c#. So mono or .net are still required. > Is that what you're > working on porting, mostly? > Right now I'm plugging a java bytecode emitter to the toolchain and porting the standard library to boo. That will be enough to get started on the jvm. Eventually the complete compiler framework will be ported to boo. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
