Navgeet-
I'm delighted to read of your interest. Please see my responses, below.
-r
On Apr 12, 2013, at 09:49, Navgeet Agrawal 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.
Codeq extends Git's universe in two directions:
- The notion of a codeq allows Git's version history to be interpreted in
terms of semantically interesting units of code.
- The ability to harvest information from multiple repos allows integration
of information from local projects, libraries, etc.
Combining these, it becomes possible to answer questions about the history of
an entire project, down to the level of (say) functions.
> 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.
I may have a broader view of program analysis than you do. Mine covers a range
of inputs, including commit history, source code, operational data, and advice
from humans. Basically, any source of information is worthy of consideration.
However, many of these inputs are far beyond the scope of a GSoC 2013 effort.
> 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.
Diffing functions over time is useful, but it is only one of many tasks Codeq
should be able to perform. The current Clojure analyzer does not harvest enough
information to resolve questions about related sets of functions, use of global
state, etc. An improved analyzer would provide leverage to Codeq as a whole.
--
http://www.cfcl.com/rdm Rich Morin
http://www.cfcl.com/rdm/resume r...@cfcl.com
http://www.cfcl.com/rdm/weblog +1 650-873-7841
Software system design, development, and documentation
--
--
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.
