You can also put a docstring in a ns form to give context. I don't think you need anything done to Clojure itself. Or more specifically, you need not be limited by whatever Clojure has done with docstrings. Nor will you need to modify defn. You can attach any metadata you like, to the vars in your program. Then your documentation report generator can use the metadata you attached. (You wouldn't generate documentation directly from the source code text, of course.) Since metadata is data structures, not just strings, the sky is the limit.
By the way, there has also been discussion of best or expected use of the :arglists metadata. Sometimes the arities you want to express in documentation differ from actual implementation, such as [& xs]. So probably you will not want a very rigid correspondence between your per-arity docstrings and the arities the compiler is aware of. -- 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.
