Now that i think of it, it is mostly a fear of having decreased productivity in writing code that affected my statement that i liked the little files. Im used to, i suppose, developing code for a specific function in a file, being able to compile, goto line numbers where there are errors, send code to slime, etc. Looking over your example made things much clearer. Its like your guiding your reader to specific parts of the 'little files', describing the theory behind them, moving on, etc. And each code fragment has a chunk name associated with it, and all of them are combined into the final .clj file using the code fragment names (in a separate chunk).
At first, i thought this would be less productive than simply putting all of the code in one clj file, but now that i think about it i think it would, with the appropriate tools. And it wouldn't even be too difficult, with org-mode (prefer it over latex any day!) Im going to start transferring a subsection of my program to literate programming, using org-mode. See how it goes... Oh, and Tim, you might want to take a closer look at org-mode. Instead of having to tangle out the code that builds everything, you could create an executable shell script block in org-mode - the makefile script could be tangled into a string using noweb syntax, and then everything could go from there. You can execute the block by hitting C- c c-c in the org file (or something like that). Pretty cool, in my opinion! -- 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
