For limitations and unimplemented features, go to the github site and check out the Issues tab and in the wiki, look at the 'To Do' page and the bottom of the 'CLR Interop' page.
I just added the non-implementation of letfn as an issue. Will be fixed shortly, probably tomorrow. (Red face, mumble, mumble, forgot to TODO that one, sigh.) Not sure why the REPL is taking so long to come back to you. I don't have that problem. My REPL is very eager to report the error. Beyond the stated issues, the biggest problem with ClojureCLR at this point is the lack of testing. It needs people banging on it, in the absence of a more complete test suite. (It does pass all the tests in the test suite, but there is a lot of ground not covered.) -David On Oct 10, 2:29 am, Dmitry Kakurin <[email protected]> wrote: > I've read "Programming Clojure" book an I love the language (and the > book), kudos! > > I'm evaluating ClojureCLR as a scripting language for my product. > Is there a list of ClojureCLR limitations and not implemented > features? > > I've just started playing with it and (after some debugging) > discovered that letfn is not implemented. > Then something else threw NotImplemeted exception. > Also when error is found it takes an enormous time to come back to > REPL (like 5-7 seconds). > > I understand that .NET port is relatively new, but I need a way to > quickly judge if it's mature enough for my purpose. > What is the best way to do it? > > - Dmitry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
