Shawn is correct across the board. A few additional comments: ClojureBox: - At this point, even an installer would be nice. Someone is working on the automating the build process, including an installer. "Any day now."
Differences between platforms: - Pure clojure should work with the exception of gen-class and less than a dozen core functions. Not much to stop development. - Platform interop: All the basics work in CLR the same as for JVM. Type hints and avoiding boxing on numerics work the same. See http://wiki.github.com/richhickey/clojure-clr/clr-interop for more details. Still missing are support for some things that the JVM doesn't support and that I haven't had time to test for (structs) or for which there is no syntax or mode of reference defined (generics, assembly-qualified names for types). - Contrib: As Shawn says, all Java interop needs to be rewritten. It's not that hard, actually, mostly just changing type hints and method names. I can translate all of core.clj and maintain all the original line numbers across more than 4000 lines of Clojure code. I started to write some notes on this. I'd be happy to finish them if someone wants to start doing this. How close is edge CLR to edge JVM? - Not counting the missing pieces, I typically run through the commits on the Clojure mothership about every two weeks or so and bring everything up to date. Fortunately, they are fairly incremental changes and go quickly. When Rich dumps out something really major-- I'm currently holding my breath on new-new/reify/...--it takes a while longer. Mono: - One BigDecimal implementation away from getting serious about this. This project is past the 90% level in functionality, but still a little shy of what the casual Clojure programmer needs to have a productive experience. To get to that stage quickly, we need some people who are willing to bang on the system, stress test it, find out what doesn't work and what's missing (things in CLR not in JVM that need addressing). There's a need for the development environment to be enhanced so the clojure programmer can be productive: porting contrib, working on SLIME, etc.) It's close, but at the moment, it's just me. Hardy adventurers, apply within. --David Miller --~--~---------~--~----~------------~-------~--~----~ 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 Note that posts from new members are moderated - please be patient with your first post. 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 -~----------~----~----~----~------~----~------~--~---
