On Thu, Dec 13, 2012 at 11:43 PM, Meikel Brandmeyer (kotarak) <m...@kotka.de>wrote:
> You can still use load to split the implementations accross different > files to keep things organised if that is your main concern. > In the early 1.0 days of Clojure, I experimented with splitting code across different files but staying within the same namespace. It was a disaster. I ran into all sorts of problems where the tooling broke down. It seemed the only reliable way to work with Clojure files was to make sure that every file had a matching namespace header at the top. Has the situation improved? (Specifically, are you speaking from experience with splitting files up in this way, or is this just a theoretical idea? If you have done this and had a good experience, what tools were you using -- emacs, eclipse, something else?) Anyway, in general, I like the idea of splitting a single namespace across multiple files and would love to hear that this is actually viable. However, for this particular project, the concrete implementations would share a lot of similar names -- it really is best to put them in their own namespaces. -- 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
