Nicola, Thanks for the very helpful comments. I'll likely proceed with the translation -- there are calls to get core.async sync'ed up with the JVM version and tools.analyzer.* has to be there.
Thanks for pointing me to the feature expressions discussion. That will be extremely useful, should it come to pass. There are some interesting problems that I'm pretty sure haven't been considered yet. The ClojureCLR lisp-reader requires an extension to symbol token lexing in order to accommodate the full range of type names in the CLR -- that will make some *.clj files written for ClojureCLR to be unreadable by other Clojure implementations even with feature expressions. There are other considerations, but I'll pursue them in that discussion. Thank you for offer to provide advice. I'll be in touch as I move this forward. -David On Thursday, August 21, 2014 7:14:15 AM UTC-5, Nicola Mometto wrote: > > > David, > > I personally have no plans to port tools.analyzer.jvm to a > tools.analyzer.clr, not for disinterest but simply because I don't know > anything about the .NET platform nor about clojureCLR. > > That said, it shouldn't be hard to port it at all, the main file to port > would be > > https://github.com/clojure/tools.analyzer.jvm/blob/master/src/main/clojure/clojure/tools/analyzer/jvm/utils.clj > > which contains most of the functions that deal with reflection on t.a.jvm, > everything else should just be a matter of replacing class names from > java.lang.* to their CLR counterpart. > > The only issue with all this, is that ATM tools.analyzer itself can only > run on clojure on the JVM because of > > https://github.com/clojure/tools.analyzer/blob/master/src/main/clojure/clojure/tools/analyzer/utils.clj#L67-L70 > > > My suggestion would be to wait for clojure 1.7 which should have support > for feature expressions and would make it possible for tools.analyzer to > be source compatible with clojureCLR too (all the code except for that > line is pure clojure, there are a bunch of instance checks for > clojure.lang.* types but it's my understanding that clojureCLR maintains > that class hierarchy). > > A relevant ticket that might add a pattern? function to core that would > solve this is http://dev.clojure.org/jira/browse/CLJ-1298 > > In any case, if you want to go ahead and start porting t.a.jvm to > t.a.clr until we wait for 1.7 and feature-expressions or `c.c/pattern?`, > feel free to contact me privately and we can discuss this further. > > Thanks, > Nicola > > dmiller writes: > > > Nicola, > > > > Excellent work! > > > > Looking forward to seeing tools.analyzer.clr in the near future. :) > > > > Well, actually, seriously, with the use of tools.analyzer.* in critical > > projects such as core.async, a port of tools.analyzer.jvm seems > necessary. > > Unless you know of plans to make a port, I'll add it to my queue. Any > > hints/suggestions/comments you can offer will be received > appreciatively. > > > -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
