Mark Engelberg <mark.engelb...@gmail.com> writes: > On Mon, Aug 5, 2013 at 11:14 AM, Timothy Baldridge > <tbaldri...@gmail.com>wrote: > >> On that subject when last discussed, it was mentioned that Clojure doesn't >> have a import * method because it's basically impossible to implement. >> > > Well, surely the word "impossible" is inaccurate, since other languages > (e.g., Scala) do it.
Slamhound does it in clojure, so it's possible and has been done. >> 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. " >> > > Maybe it's not ideal if Clojure has to walk the classpath, but the > alternative is that I have to manually walk the classpath and jars myself > with no idea what I'm looking for. Surely it's better for this to be > handled through an automated process. Yep. The only argument is whether it should be a language feature or an IDE feature. Phil -- -- 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.
