On May 14, 2015, at 12:37 PM, Erik Price <e...@zensight.co> wrote: > The code itself is mutable. The nice thing about a private function is that I > have reserved the right to change how it works someday, without fear that > others have become dependent on the way it currently works.
That’s why I suggested foo.api and foo.impl namespaces and requiring (convention, peer review) that nothing outside of foo.api uses the foo.impl namespace — any exceptions would need to be specifically discussed and sanctioned. And remember there’s a difference between building a library for "the public" to use and building software for internal use by your own team or other peer teams in your division. Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
