On May 17, 2:19 pm, Paul Mooser taron...@gmail.com wrote:
Is anyone having contrary results, or does anyone know of a way to
call add-classpath and have it actually work with an up-to-date trunk
build of clojure ? This basically breaks my common usage of clojure,
because it requires me to
Thanks for the reply, Rich - I'll have to see if I can find another
way to get this to work.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Clojure group.
To post to this group, send email to
Thanks for the reply, Rich.
I'll have to see if I can find another way to make this work, but it
has been really nice so far having the ability to add things to the
classpath that weren't specified at launch time.
Most of what I am doing is in fact at a REPL, because I have clojure
embedded
Is anyone having contrary results, or does anyone know of a way to
call add-classpath and have it actually work with an up-to-date trunk
build of clojure ? This basically breaks my common usage of clojure,
because it requires me to pass all class paths to the app upon
launching, which isn't
Hi,
Am 16.05.2009 um 06:32 schrieb Paul Mooser:
I've been using clojure for a while at this point, and the approach
I've settled on launches clojure using -cp clojure.jar, and then my
user.clj file contains code that loads a bunch of thing into my
classpath.
After updating to r1369, which
Hi again,
I think I found the root cause of my problem.
Since clojure compiles namespaces as they are encountered it
depends on when c.c.def is compiled. If it's compiled first, it's
anonymous function is created in clojure.core. Hence you get
the clojure/core$clojure_contrib_def_... .class
I've been using clojure for a while at this point, and the approach
I've settled on launches clojure using -cp clojure.jar, and then my
user.clj file contains code that loads a bunch of thing into my
classpath.
After updating to r1369, which made some changes to classloaders that
I don't claim
