> Every launch of Clojure has the opportunity to specify a classpath to
> use. Since user.clj is loaded from classpath, it seems to me that's a
> sufficient mechanism to avoid loading a given user.clj for a given
> launch of Clojure.
Sure, I can definitely control the loading of user.clj. I made the
proposal because on a couple of occasions I did not take explicit
steps to either load or avoid loading user.clj, and spent some time
trying to track down my resulting problem before I realized what had
happened (others have also had issues with user.clj loading, see
http://groups.google.com/group/clojure/browse_frm/thread/6951a19912adfb8a/a9076dbb616144bf?lnk=gst&q=user.clj#a9076dbb616144bf).
I have a user.clj for convenience in REPL sessions, which is the case
where auto-load of user.clj makes sense to me.
>I think the convenience of the user.clj "hook" file
> being auto-loaded very early in launch is significant.
Could you share what benefits you get by the auto-load of user.clj
early in the launch process? In my applications, I explicitly load
libs I need, so it seems that if needed I could explicitly load
user.clj for a non-repl application and get the same result as the
auto-load.
Thanks.
--~--~---------~--~----~------------~-------~--~----~
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
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
-~----------~----~----~----~------~----~------~--~---
