An alternative solution to trying to make macros opaque is just to disallow the macros which depend on disallowed functions. It should be a relatively simple matter to generate this list programmatically from clojure.core source. So instead of just saying "You can't use count." It would say "You can't use count or for."
That at least would solve the cognitive dissonance that happens now where you submit an answer that doesn't violate the rules directly. Although it doesn't perhaps introduce a much lesser one which is why is this unrelated function disallowed? I think perhaps this is just waiting on someone to submit a patch :) jack. -- 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
