It's interesting that most of the solutions presented here involve something along the lines of immigrate / potemkin / redefine (in your piplin code). With so many people reinventing the same wheel, it would seem that this really is a key piece to solving the problem of putting a friendly API on top of functions that implementation-wise are split across a number of namespaces. Makes me think that this is an important enough tool to be in core.
On Thu, Dec 13, 2012 at 5:22 PM, dgrnbrg <dsg123456...@gmail.com> wrote: > I've written a large application that uses this approach. You can see it > applied with protocols and multimethods in types.clj and protocols.clj, and > the remainder of the code in types/*.clj. I used this to manage over 10 > different extensions, and it's been simple enough to keep organized. > > I have used a few techniques to tie together all the disparate files. I > have an approach for vars/fn from other namespaces, even if they're > dynamic, and organization/readability in the face of a large API. > > You can find that here: > https://github.com/dgrnbrg/piplin/tree/master/src/piplin > -- 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
