2 ms·

On Clojure documentation: * There is a very informative book about clojure by Stuart Halloway: http://www.pragprog.com/titles/shcloj/programming-clojure http:/

On Clojure documentation: * There is a very informative book about clojure by Stuart Halloway: http://www.pragprog.com/titles/shcloj/programming-clojure http://www.pragprog.com/titles/shcloj/programming-clojure * http://en.wikibooks.org/wiki/Clojure_Programming http://en.wikibooks.org/wiki/Clojure_Programming * http://www.google.com/#hl=en&q=clojure+tutorial http://www.google.com/#hl=en&q=clojure+tutorial Take your pick.

mahmud 17y ago
I hate to nitpick, and I am sure many of those documents will grow into something fantastic, but the difference between Lisp documentation and "scripting language" documentation is one of caliber. Compare any existing clojure documentation to any of these traditional Lisp specifications: http://library.readscheme.org/papers/t_manual.pdf http://library.readscheme.org/papers/t_manual.pdf http://www.franz.com/support/documentation/8.0/ansicl/ansicl.htm http://www.franz.com/support/documentation/8.0/ansicl/ansicl... http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-2.html#node_toc_start http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-2.html#node_toc... http://www.opendylan.org/books/drm/ http://www.opendylan.org/books/drm/ Then google the manuals for the "lesser" Lisps; ISLisp, EuLisp and LeLisp. I.e. A manual; specification + examples, etc. Lisp texts have a specific flavor and you wont mistake them for others. It doesn't have to be written by Guy Steele or Kent Pitman for it to be useful, by the way :-P It's not as codified as the Unix manpage format. In a nutshell, Lisp manuals usually go this way; a short introduction to the Reader syntax; an overview of the special forms; high-level description of the type system; in depth discussion about the evaluation model and all top-level forms, then In depth discussion about the language specified parts of the type system over several chapters. Each identifier is clearly labeled by its type and evaluation method, e.g. special variable, generic function, condition, etc. Its uses and abuses. Its side-effects, if any. Its exceptional situations, what conditions it might raise, if any. Examples. And finally links to other related symbols. Nothing is said about regular expressions, database access, web API or GUI toolkit. A Lisp documentation is sufficient for implementing the language, as well as daily use. That's really the main difference I can think of. The C book by Harbison and Steele C: A Reference Manual is the closest thing I have seen to a Lisp-style manual for a non-Lisp programming language, and it's no coincidence ;-) Regards.

mahmud 17y ago

I hate to nitpick, and I am sure many of those documents will grow into something fantastic, but the difference between Lisp documentation and "scripting language" documentation is one of caliber. Compare any existing clojure documentation to any of these traditional Lisp specifications: http://library.readscheme.org/papers/t_manual.pdf http://library.readscheme.org/papers/t_manual.pdf http://www.franz.com/support/documentation/8.0/ansicl/ansicl.htm http://www.franz.com/support/documentation/8.0/ansicl/ansicl... http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-2.html#node_toc_start http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-2.html#node_toc... http://www.opendylan.org/books/drm/ http://www.opendylan.org/books/drm/ Then google the manuals for the "lesser" Lisps; ISLisp, EuLisp and LeLisp. I.e. A manual; specification + examples, etc. Lisp texts have a specific flavor and you wont mistake them for others. It doesn't have to be written by Guy Steele or Kent Pitman for it to be useful, by the way :-P It's not as codified as the Unix manpage format. In a nutshell, Lisp manuals usually go this way; a short introduction to the Reader syntax; an overview of the special forms; high-level description of the type system; in depth discussion about the evaluation model and all top-level forms, then In depth discussion about the language specified parts of the type system over several chapters. Each identifier is clearly labeled by its type and evaluation method, e.g. special variable, generic function, condition, etc. Its uses and abuses. Its side-effects, if any. Its exceptional situations, what conditions it might raise, if any. Examples. And finally links to other related symbols. Nothing is said about regular expressions, database access, web API or GUI toolkit. A Lisp documentation is sufficient for implementing the language, as well as daily use. That's really the main difference I can think of. The C book by Harbison and Steele C: A Reference Manual is the closest thing I have seen to a Lisp-style manual for a non-Lisp programming language, and it's no coincidence ;-) Regards.