Hi guys, Maybe we'll see some change in the future, Atlas<http://www.clojureatlas.com/> already seems to be interesting. I think there is also a huge potential with Codeq. >From what I gather Codeq only parse thing looking like (defsomething ) for now. But we can imagine that if we augment the capability of it, we could extract docstrings, symbols utilisation to connect the different parts of a code base, etc... I think there might be a Google Summer of Code project like that.
The cool things about Codeq are: - it doesn't need anybody "in control" of Clojure to work on such a project - we can add to the Codeq schema other documentation attributes than docstrings to replace broken or insufficient documentation (still on our own) - it surely as great potential to explain the code base of a project with the fact that it can highlight evolution of the code at a higher level than just git diffs - and it could be run on the core clojure libraries of course And I don't think that I thought of all the things we could do about it but I think it might be the new way to generate documentation for code, a highly queryable one at that. The only issue, it's not done yet... :-D Cheers -- -- 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/groups/opt_out.
