On Tue, Jul 23, 2013 at 3:26 PM, Gary Trakhman <gary.trakh...@gmail.com>wrote:
> What's problematic about it is that it's slightly easier to do the wrong
> thing. It seems insignificant, but 98% of times you use use, it's going to
> be wrong. Also, 'use only' means I have to change my calling NS twice in
> different parts of the emacs buffer any time I change a function name in
> the called namespace.
>
>
> On Tue, Jul 23, 2013 at 3:08 PM, Cedric Greevey <cgree...@gmail.com>wrote:
>
>> :use...:only doesn't strike me as especially problematic, since it
>> documents the specific symbols it's importing and from where.
>>
>
Is it "wrong" 98% of the times you use ":use...:only"?
And if you change the name of the function "fnname" where it's defined,
yeah you'll have to change "fnname" wherever it's used as well, whether
those uses say "fnname" or "mylib.core/fnname" or "m/fnname" or even
"(:require [mylib.core :refer :rename {fnname othername}])".
Of course, the latter suggests the question of whether it's "wrong" to use
:require ... :refer :only as well. :)
--
--
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.
