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.
On Tuesday, 6 August 2013 07:04:16 UTC+12, puzzler wrote: > > On Mon, Aug 5, 2013 at 11:31 AM, Jonathan Fischer Friberg < > odys...@gmail.com <javascript:>> wrote: > > I think it's java that is at fault here. I think wildcards should never >> have been part of java to begin with. The argument here is basically >> exactly the same as why :use shouldn't be used, so I wont explain it >> further. > > > Well, Clojure is hosted on Java and clean interop is one of its goals. > > The fact of the matter is that many Java libraries are designed and > documented with the existence of the wildcard in mind. The code is > fragmented across many small classes that are designed to be imported en > masse with a wildcard. The documentation often does not even provide any > details about which specific classes are located where, it simply shows to > use the wildcard to get them all. > > Whether this is Java's "fault", the fact that Clojure does not embrace > this idiom has concretely hurt my ability to use Java code. > -- -- 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.
