On Apr 16, 2013, at 04:54, Navgeet Agrawal wrote: > Hi all, thanks for these suggestions and sorry for the late reply.
No problem; I'm happy that we didn't scare you away (:-). > I have been looking into jvm.tools.analyze for the past few days and it > looks as a better choice to build a comprehensive analyzer. Of course > the biggest problem in using it is it likes to expand all macros fully, > which is bad for codeq. I think that can be handled by patching some > parts of Compiler.java and using the patched methods. I am currently > trying to write a demonstration fork of jvm.tools.analyze. >From a documentation point of view, macros have two operational contexts. In one, they generate code; in the other, the generated code is run. I'm not precisely sure how this should be handled, but it _is_ interesting. > I have been thinking for some time that tracking the inputs and outputs > through every function in a program over time can be useful. We could > allow the user to call some function with test input, then for all > functions down the call chain, store their input and output in the > datomic database. Do this for every commit (every time the function > changes). The results can provide feedback about data flow in the > program across commits. Any comments? One use case for this sort of tracking would be to collect "signatures" for the inputs and outputs seen in the test suite. If a production run generates diverging signatures, either the test suite is incomplete or the production code is using the function in an unexpected fashion. > That's all for now till my exams end. Good luck in the exams! -r -- 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.
