Hi John, On Fri, Oct 23, 2009 at 8:08 AM, John Harrop <jharrop...@gmail.com> wrote:
> I think we need some notion of semi-private as well. It would be ignored by > :use and by automation like tab-completion of symbols, doc generation, and > the like (except it would show in tab-completion inside of its namespace) > but would not actually be illegal to invoke from elsewhere. So, it would be > like private in every respect except for invokability. > The purpose being so that you can make support functions (and perhaps other > things) for macros without cluttering up the publicly-visible symbols list > of the namespace, that is the set exported via :use and :require :as and > affecting tab-completion and documentation generation. > Other solutions are to use @#'ns/private-var to access private vars from the macro or to make the macro shallow using a public (usually higher-order) helper function (is this possible in the general case?). Christophe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
