The CLojureCLR code was my contribution. I'm still working on it. AFAIK, no one else is. After I get the next release out, I hope some others might be tempted to get involved.
I almost had the CLR version working on the new lazy code, but ran into a change that Rich made (allowing a user-specified base class for (fn ...) implementations) that broke some workarounds (to DLR limitations) in my code. So I finally bit the bullet and completely rewrote the compiler. This was going to have to happen eventually. In addition to fixing the breakage: the compiler code is more closely aligned with that in ClojureJVM so that changes can be more easily brought over; type inferencing is greatly improved; and AOT- compilation will now be possible. Right now, performance is not where it should be. Some of that will be code generation issues that can be fixed pretty easily--some unnecessary casts, etc. Some of it is DLR/Reflection.Emit/JITter overhead that is going to be more difficult to cure. I've identified several strategies to improve this performance. There will probably be different compilation modes depending on the context: a 'light' mode for the REPL, for example, and a 'heavy' mode for AOT compilation. (For comparison, it appears that IronPython, also built on the DLR, has four compilation modes.) Once I have the two basic modes ready, we'll be able to play with varying strategies of compilation. (The primary dimensions of interest involve how IFns are implemented, which involves an interplay of techniques for constant initialization and referencing and closed-over variable implementation.) I've lost about 4 weeks out of the last 2.5 months to travel and some work obligations, so this has taken longer than expected. However, that load lightens after this week, so I should be able to crank away again. A few weeks more to workable code. Then maybe somebody with greater competence on CLR internals will get interested. David On Apr 26, 6:33 pm, "Matthew D. Swank" <akopa.gmane.pos...@gmail.com> wrote: > Given the recent dust-up on c.l.l about the platform independence of > clojure, I was wondering anyone was still hacking on the CLR code > base. The stuff in contrib doesn't seem to have changed since it was > checked in February. > > Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
