Another view. On 25 May 2010 07:25, ka <sancha...@gmail.com> wrote: > Tim, > > I don't know much about either lisp or latex :). But it looks like a > really neat idea at a first thought to me. Have two remarks- > 1. From the developer's pov - I'm not sure how the developer, who is > accustomed to looking at just code + some comments, will manage > working with the book. But your "tangle" step might help here.
Don't forget the weave step too. http://en.wikipedia.org/wiki/Literate_programming The basics are write the two together. Then programmatically extract one or both as separate entities. Or read the original combined. > 2. From the user's pov - Users will still look for small snippets of > docs like - http://clojure.org/reader; not everyone will have to > patience to go through an entire "chapter". How do you think we can > extract just these small snippets from the whole book? <quote>A preprocessor is used to substitute arbitrary hierarchies, or rather "interconnected 'webs' of macros",[4] to produce the compilable source code with one command ("tangle"), and documentation with another ("weave"). </quote> Depending on the language used to wrap the documentation and the code. So given a good programmer, who keeps the documentation up to date, then extracts and tests the code.... You have a system that is long lived and contains the history for those who want it, the user manual etc etc. HTH -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk -- 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
