I would like a zip of DLLs that are as widely compatible as possible across CLR/DLR versions accompanied by a clear list of which versions are compatible.
Regarding releases, I'm glad to lag behind the bleeding edge by a lot in order to have a stable platform. What I want to be able to do is grab the DLLs, add them as references to my VS project, and compile, much like I do with NetBeans and the JVM clojure. I have to admit that I haven't tried ClojureCLR since right around the 1.1 release, so I don't remember the details of the problems that I encountered. I am in the process of migrating a lot of stuff from VS 2008 to VS 2010. Once I finish that I will try ClojureCLR again and get back to you regarding embedding and AOT. On Aug 3, 3:11 pm, dmiller <dmiller2...@gmail.com> wrote: > I can move creating a binary distribution to the to top of the list. > > I could use some guidance from the interested on what would serve the > purpose on this and other things mentioned here. > > on the distribution: Do you want just a zip of of DLLs? An > installer? Do you want installation to the GAC? > > on 'stable, dependable': Is there any strategy on creating new > releases that makes sense? Assume anyone wanting to stay on the > bleeding edge will build for themselves? > > start-up speed: I'm running some experiments on that. The problem > is mostly the monolithic nature of the assemblies created and the > amount of environment initialization. Suggestions welcomed. > > Ease of embeddability: please elaborate on the problems. > > AOT'ing clj files: Ditto. > > -David > > On Aug 3, 12:47 pm, Timothy Baldridge <tbaldri...@gmail.com> wrote: > > > > I really wish that ClojureCLR had a binary distribution. I like > > > clojure a lot but I have a .Net background and a lot of .Net code to > > > interact with. If ClojureCLR had a stable, dependable binary > > > distribution I would be able to use it at work much more than I > > > already do. I don't care much about 1.2 features like defrecord. What > > > I care about is start-up speed, ease of embeddability, and Visual > > > Studio integration (not Intellisense, just AOT'ing .clj files). > > > +1 for all of that > > > That paragraph basically explains why I haven't started using clojure > > at my work yet. > > > Timothy Baldridge -- 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
