On Wed, Mar 13, 2013 at 9:52 AM, Ambrose Bonnaire-Sergeant <abonnaireserge...@gmail.com> wrote: > How useful is a fully macroexpanded AST to Codeq? There are line numbers > associated > with the AST nodes, and column numbers if you're using Clojure 1.5.0+.
I am strongly of the opinion that macroexpansion should not be part of a codeq's core definition. First off, it is not the minimal thing we need to get useful dependency analysis done. What we really need is the non-macro-expanded sub-codeqs. Also, it's just a huge can of worms. You would need a new hashing function that would be invariant to gen-sym suffixes. More importantly, where do you draw the line when there is recursive subexpansion of nested macros? Do capture the whole evaluation tree? And how do you relate that back to the original code? Capturing only some of the dependencies would seem to miss the point. Interesting questions, but we shouldn't let them hold up the basic steps. > Ambrose > > > On Thu, Mar 14, 2013 at 12:48 AM, Rich Morin <r...@cfcl.com> wrote: >> >> On Mar 13, 2013, at 09:21, Ambrose Bonnaire-Sergeant wrote: >> > I have two recently created contrib projects to help use analysis >> > results for Clojure and ClojureCLR. >> >> Have you considered whether an how this information could be used >> as part of Codeq's analysis phase? For example, how hard would it >> be to relate the AST to specific line and column numbers? >> >> -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. >> >> > > -- > -- > 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.
