On Tue, Sep 7, 2010 at 11:10 PM, Mark Engelberg <mark.engelb...@gmail.com> wrote: > Files: > Many times there are dozens of functions that are interrelated. Only > one or two of them are the crucially important "entry points" that > provide the high-level API. The rest are mostly helper functions that > implement the lower-level details. They are made public because in > some situations, you might want to have access to those lower-level > details, but 99% of the time, you can ignore them. By default, all of > these functions will show up in an auto-generated API listing.
Full ack here. There are functions I want to mark private to protect from external use, but I still want to be able to use from different namespaces inside a given library. Perhaps we need a metadata key like :internal to signify that a function should be considered private for purposes of documentation? -Phil -- 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
