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 <armando_blan...@yahoo.com> wrote: > The Java compiler doesn't like it; it won't import it from other > packages. The JVM won't mind. When Clojure code is the consumer, or > with use/require Clojure libs, one-segment namespaces work fine. I > keep a lot of those for test/hacks/trying things out, aot compiled and > not. > > On Aug 12, 5:09 am, Meikel Brandmeyer <m...@kotka.de> wrote: > > > > > Hi, > > > it's for technical reasons. Clojure wll then generate classes without > > a package, which causes them to be put in the default package. There > > are problems/restrictions/issues with classes in the default package. > > I'm not a JVM expert, so someone else might provide more details. I > > just go with the "JVM doesn't like it. Don't do it." > > > Sincerely > > Meikel -- 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
