Comments on: Design By Contract with Clojure http://www.objectcommando.com/blog/2010/03/07/design-by-contract-with-clojure/ languages, development and design Thu, 12 Aug 2010 14:20:44 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Ryan http://www.objectcommando.com/blog/2010/03/07/design-by-contract-with-clojure/comment-page-1/#comment-139 Ryan Tue, 09 Mar 2010 01:30:46 +0000 http://www.objectcommando.com/blog/?p=190#comment-139 Thanks for the correction! I updated the post to add the caveat. Thanks for the correction! I updated the post to add the caveat.

]]> By: Alex Stoddard http://www.objectcommando.com/blog/2010/03/07/design-by-contract-with-clojure/comment-page-1/#comment-138 Alex Stoddard Mon, 08 Mar 2010 21:11:13 +0000 http://www.objectcommando.com/blog/?p=190#comment-138 I have been looking at the clojure pre and post conditions too. One caveat, they look like regular metadata but they are not. Asking on the #clojure IRC channel revealed they are currently implemented by compilation into the function at the time of definition. The original condition definitions are available as metadata on the arglist of the function (where the arglist is itself metadata of function) e.g.: (map meta (:arglists (meta #'foo))) But that is just reporting, you can't currently modify the pre/post conditions associated with a function. I have been looking at the clojure pre and post conditions too. One caveat, they look like regular metadata but they are not.

Asking on the #clojure IRC channel revealed they are currently implemented by compilation into the function at the time of definition.

The original condition definitions are available as metadata on the arglist of the function (where the arglist is itself metadata of function) e.g.:

(map meta (:arglists (meta #’foo)))

But that is just reporting, you can’t currently modify the pre/post conditions associated with a function.

]]>