


I guess I'm looking for something like this answer on Swank, but the tools seem to have moved on since then. Clojure Programming has a whole chapter on organising and building projects, but it is so comprehensive that conversely I'm finding it difficult to tease out the information relevant to me now. With R I can get away with a file of plain text containing the bulk of the code, perhaps with one or two others containing common functions for larger projects.Ĭlojure is very different and with no experience in Java I am struggling to put the pieces together.
#EMACS CIDER DOWNLOAD CODE#
Obviously the thing to do is to get stuck in and experiment with code exercises and small tasks, but the immediate problem for me has been the complexity of structuring, organising and even just plain running projects in Clojure.

I have found them promising but I am getting lost in the detail. I have bought Clojure Programming and the Clojure Data Analysis Cookbook and dipped into both. I'm using Emacs 24.3, cider 20131221 and Leiningen 2.3.3 on Java 1.7.0_45 Java Hotspot 64-bit server. I'm not a professional developer but I have several decades of programming experience (ARexx, VB/VBScript/VBA, then Perl and daily use of R starting in 2011). I have just begun to learn Clojure, motivated in part by this essay. Apologies in advance for the somewhat discursive nature of this clump of related questions I hope the answers will be a useful resource for newcomers to Clojure.
