Hi Navgeet,
I'm glad you found codeq-playground helpful. It looks like you've found Rich Morin's wiki. Did you also see his codeq-cookbook project? When you said analysis I had something else in mind: check out https://github.com/clojure/jvm.tools.analyzer I wonder about how that could be used to add more queryable information during analysis. At the very least it might spawn new questions to answer. I'd also suggest checking out things like kibit. I have no idea where that will take you, but I'd be surprised if there aren't some interesting applications for core.logic. Clojail is the last one I'll mention. Could some kind of automated runtime evaluation based on analysis yield some interesting results? Just brainstorming here, but best wishes. Devn — Sent via Mobile On Fri, Apr 12, 2013 at 3:41 PM, Navgeet Agrawal <navgeet.agra...@gmail.com> wrote: > Hi all, I came up across the project idea for a Program analysis suite > based on Codeq [1] a week ago and have been working on it since. > The idea appealed to me instantly, since I had just started to look into > program analysis possibilities, and analysing a (or many) repository's > version history is a novel approach in itself. > I have already gone through Datomic, codeq and codeq-playground [2], and I > fully understand codeq's schema and the current clojure analyzer. Regarding > my experience with clojure, I have been reading through Deuce's [3] source > code since a month or two, and I have some experience with Ruby aside from > the usual C and C++. > I am currently going through all of the pages under [4] and there are a lot > of ideas suggested there. I am not sure how many of those ideas are > suitable for implementation in a program analysis suite, since many of them > are about harvesting documentation and metadata from a repository. > As far as the current clojure analyzer is concerned, I understand that all > it does is to harvest the names and sources of all `def` and `ns` forms. > While it is possible to analyze furthur and create a tree of codeqs, with > leaves consisting of symbols, I am not sure what leverage it provides > against getting a diff of a function between two commits. > Thanks, looking forward to your suggestions. > [1]: > http://dev.clojure.org/display/community/Project+Ideas#ProjectIdeas-ProgramanalysissuitebasedonRichHickeysCodeq > [2]: > https://github.com/devn/codeq-playground/blob/master/src/com/thinkslate/codeq_playground/core.clj > [3]: https://github.com/hraberg/deuce > [4]: http://wiki.cfcl.com/bin/view/Projects/Codeq > Navgeet Agrawal > https://github.com/Navgeet > -- > -- > 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. -- -- 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.
