I'm trying to build something related [1]: A temporal- and control-flow reasoner for software in general. My idea was to tie this into logging or debugging interfaces. I would be very, very interested in combining this with source-code reasoning (which might also profit from some shared higher-level logic), yet inexperienced.
I started prototyping two days ago, I haven't even gotten around to doing the temporal- and control logic yet, but already I am bumping up against - and feeling my way into - questions concerning the design. So if you, David or someone else knowledgeable were available for brief questioning and guidance I'd be very grateful. All the best, Gabe [1]: Prototyping: https://github.com/werg/herpderp On Fri, Mar 30, 2012 at 9:58 PM, David Nolen <dnolen.li...@gmail.com> wrote: > http://soft.vub.ac.be/SOUL/ > > This project is worth looking at for directions that kibit might want to > go. It's also a good resource for cool ideas on how to leverage core.logic > - miniKanren was designed from the get go to manipulate Lisp source. > > David > > -- > 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 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
