I've used Java since 1.0 days which is a depressing long time ago. In that time, I've used and seen used * an awful lot. Of course, it's bad (when 1.2 came out, we all had to fix our code because of the java.awt/java.util List nameclash), but the alternative was a total pain in the ass.
I stopped doing this around 2004, when Emacs started resolving the imports for me. Currently, maintaining Java imports in Clojure feels like it did with Java before 2004. Stefan du Fresne <stefan.du.fre...@gmail.com> writes: > Just a note: my understanding was that even in Java-land using import * is > not recommended. I've done professional Java development since 2006 and in > that time I don't think I've ever used import *. I've certainly seen it *in > *production code, but I've never felt the need to use it myself. > -- -- 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.
