http://clj-me.cgrand.net/2008/05/28/multimethods-arent-magic-nor-mutable/ When the pupil is ready to learn, a teacher will appear. Mon, 30 Jan 2012 20:57:36 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://clj-me.cgrand.net/2008/05/28/multimethods-arent-magic-nor-mutable/comment-page-1/#comment-2 Rich Hickey Sat, 31 May 2008 13:39:00 +0000 http://clj-me.cgrand.net/2008/05/28/multimethods-arent-magic-nor-mutable/#comment-2 You are right - the correct thing to do is use the var - #'foo. This is a specific case of the more general problem of building long-term connections to function objects. Saying (map foo ...) is fine, as foo is unlikely to change (nor would you want to see it change) during the execution of map. But when you 'capture' the value of a var containing a fn (as the call to comp does here), and store it away for use later, you probably want the var itself instead, as it will reflect redefinitions and bug fixes. Macros are not the answer here. You are right – the correct thing to do is use the var – #’foo. This is a specific case of the more general problem of building long-term connections to function objects. Saying (map foo …) is fine, as foo is unlikely to change (nor would you want to see it change) during the execution of map. But when you ‘capture’ the value of a var containing a fn (as the call to comp does here), and store it away for use later, you probably want the var itself instead, as it will reflect redefinitions and bug fixes. Macros are not the answer here.

]]>