Thanks for the suggestion(s), but I don't like the idea of writing custom code to implement better doc strings. Should any breaking changes occur in Clojure core, then I too could be forced to make changes and deal with broken code everywhere. If there was more community interest and the Clojure team implemented it then I'd be good because I know it would be maintained, but it doesn't seem like this is the case. So if it requires some custom work then I think I'd much rather do it at the tooling level as a plug-in to an editor. Ie, pull doc strings out all together and have them linked to and stored elsewhere... Maybe just store a db id in the doc string and go from there. I'll need to mull it over ;)
Thanks, tim -- 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.
