On Aug 5, 2013, at 2:14 PM, Timothy Baldridge wrote: > > To quote Rich: "Java packages are not enumerable. The only way to do so is to > walk the classpath/jars etc. I don't think import * is a good idea, as it > brings more into a namespace than you are going to use, making Clojure's > namespace enumeration, e.g. ns-imports, that much less useful. " > > https://groups.google.com/forum/#!searchin/clojure/import$20wildcard/clojure/-gCg_0wmT5o/LnxDCU6W538J
I think that was the old discussion that I remembered and mentioned in a previous post. Now that I look back at it and see that this was only about "import" l wonder: Is there a similar aversion to allowing wildcards in :require/:use specifications? I see that that the discussion about import is continuing as I type, and I'd personally be pro-wildcard in all cases, but perhaps these are separate issues and wildcards might be allowed in :require/:use however that turns out? -Lee -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
