On Nov 12, 8:29 am, Sean Devlin <francoisdev...@gmail.com> wrote: > Rich, > Just read the section on reify. I'm not quite sure what this new > mechanism lets me do. Could you provide an example of the problem it > solves? I personally would benefit from seeing the "Old, painful way" > contrasted to the "New, awesome way". This would probably help with > the other features too. >
reify is the most subtle, as it is a subset of proxy, limited to implementing interfaces only, and less dynamic (no equivalent to update-proxy). What you get in return is a construct with fewer host implications, and much better performance, as stated in the wiki doc: "The result is better performance than proxy, both in construction (proxy creates the instance and a fn instance for each method), and invocation. reify is preferable to proxy in all cases where its limitations are not prohibitive." Rich -- 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
