1. CLR Interop: Interop is the focus of development at the moment. Work is progressing on those things that the JVM implementation doesn't worry about: ref/out params, assembly references, generics, etc. I haven't spent much think time on attributes yet. Do you have some specific use cases? That would be stimulating.
2. Performance goals: Clojure:Java::ClojureCLR:C#. Not there yet, but no reason why this is not achievable. If you look at the IL generated, ClojureCLR is almost identical to ClojureJVM. At this point, I consider interop the bigger impediment. The game plan for the near future: Interop, implementing the new deftype/reify/protocol goodness, then maybe performance. deftype/&c affect IL generation, so I'd like to get that done before coming back to look at the grungy details of whether or not the CLR is inlining some little thing. 3. I'll let the folks who are better at Clojure programming style answer this one. -David M On Dec 1, 11:41 pm, Mike K <mbk.li...@gmail.com> wrote: > Hi Clojurites! > > I'm reading about Clojure and ClojureCLR with great interest. Since > I'm a .net developer with little Java / JVM experience, I'm > particularly interested in ClojureCLR. It seems like David M. and > crew are doing a fantastic job with the CLR implementation! A few > quick questions: > > 1. Re. CLR Interop -- one thing I didn't see mentioned on the wiki > is .net attributes (metadata). Will annotating methods, properties, > etc with attributes be supported? > > 2. What are the performance goals for ClojureCLR? I saw a video > overview of Clojure by Rich in which he stated (perhaps with certain > caveats that I don't recall) that essentially Clojure ran at speeds > comparable to Java. Is having ClojureCLR run at speeds comparable to > C# a realistic goal? What's the current performance story? > > 3. I get the basic concept that native Clojure data structures are > immutable and persistent. This is obviously an impedance mismatch > when dealing with JVM or .net objects and APIs that are built around > mutable state. Where can I more info regarding best practices in > getting these two different animals to work well together within an > app? > > Thanks, > Mike -- 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
