On Sat, Nov 14, 2009 at 1:42 PM, Richard Newman <holyg...@gmail.com> wrote:
> I like CL's package support for this kind of situation, where > unexported symbols can still be reached via foo::bar, at the cost of > an obvious "code smell". This suggests an alternate fix for the private functions in macros problem: 1. Keep the throw when dereferencing another ns's private vars. 2. Add a way to override that throw when dereferencing -- a "deref-private" that always works. 3. Add a reader macro, say #!, with the property that #!foo expands to (deref-private #'foo). 4. Macros can use #!priv-fn in their expansions to produce an expansion that calls a private function without issues. 5. #! outside of this circumstance would be a code smell. 6. Optionally, syntax-quote, when resolving symbols into fully qualified ones, might auto-#! all that reference private vars IN THE CURRENT NAMESPACE. Then no explicit #! is needed on the hypothetical priv-fn in the macro: `(priv-fn foo ~bar) instead of `(#!priv-fn foo ~bar). At the same time, referencing a *foreign* private function in a macro still needs the #!.Then #! is ALWAYS a smell. -- 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
