On Sun, Nov 11, 2012 at 2:26 PM, Mark Engelberg <mark.engelb...@gmail.com> wrote: > I can relate to Denis' issue. I find it pretty common to have a common set > of dependencies across every file in a project.
Well, I have to say I was puzzled by Denis' post because I definitely don't have common dependencies across every file. Now hearing you say the same thing I'm doubly puzzled... I don't like to have anything imported that I'm not explicitly using (and I regularly double-check after refactoring to make sure I remove any redundant imports). Preferences aside, however, I'm genuinely curious as to the sort of program structure that has the same dependencies in every namespace. I can see how some of Denis' imports are useful for the repl - but I tend to just import them as needed or write them out in full (clojure.pprint/pprint is my most common one) - but I'm a bit surprised to see set, string, xml, sh and io all being that common (in every file). Denis, Mark, could you speak to what sort of things you're using these for that make it convenient to have them in every namespace? I tend to have I/O isolated to one or two namespaces, the same goes for shell operations, and XML operations. Maybe we're working in different enough fields that our use cases are very different (I suspect that's true for Mark - not sure what area Denis works in?). -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "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
