On Fri, Jun 11, 2010 at 10:29 AM, Tom Faulhaber <tomfaulha...@gmail.com> wrote: > Nice! I think this kind of functionality should end up getting > promoted. I have also written this a couple of times and thought about > generalizing it. I'm glad you did.
Cool. I'm not sure how broadly-applicable it is--you want it when you're building programs that are designed to be extensible with plugins like Leiningen (or Emacs; it's inspired in part by defadvice), but I'd be reluctant to suggest it for projects where you have control over the whole thing. I'd also be reluctant to have it promoted in such a way that I couldn't fix bugs or make further improvements to it anymore. But on the other hand it's only 30 lines or so; there's probably not a whole lot more I'll do with it. > This could also serve as the basis for some nice tracing functionality > (esp. combined the clojure.contrib.logging). You'd want to wrap the > hook function with a macro that also captured the function name and > maybe arglist metadata. Anything that the current c.c.trace lib doesn't have? -Phil -- 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
