Re: What is the good way of def-ing during macro expansion

Hi Nicolas, > What I do currently: > I keep all the constant definitions and the rules definitions in an > atom and at the end, I call a macro at top level that define > everything, in the dependency order. Would you mind posting an example of this? That would definitely help me to better underst

Re: What's a single-segment namespace and why should it be avoided?

Thanks for responding. I'm glad to know this is about technical limitations rather than some preference for deeper namespace hierarchies. On Aug 12, 2:42 pm, Armando Blancas wrote: > The Java compiler doesn't like it; it won't import it from other > packages. The JVM won't mind. When Clojure code

What's a single-segment namespace and why should it be avoided?

I've seen recommendations around not to use single-segment namespaces [1]. What exactly is a single-segment namespace and why should I avoid using them in my projects? My guess is that a single-segment namespace is one that's completely flat instead of hierarchical, as if I were to put my source i