#clojure logs

2008-06-24

08:50cemerickIs there a function or var available that contains the path to the current file?
08:50cemerick(current file being loaded, I should say)
09:18rhickeycemerick: not officially - (.get clojure.lang.Compiler/SOURCE_PATH) will work
09:20arbschtcgrand: thanks for the correction :)
09:22cemerickrhickey: Hrm. I think I'll skip that for now. FYI, I'm setting up a build process so that gen-and-save-class forms can always use a consistent output path, regardless of where the .clj files are. For now, I'll just always use "." for the output path, and run that process at the package root.
09:22cemerickHaving a clojure/*file* var that files can reference as they're being loaded would be super-handy. :-)
09:22rhickeyyes
11:15cgrandrhickey: about reduce, what I still doesn't understand is that, sometimes, the seq wasn't retained -- hotspot JIT voodoo?
11:16cgrandfor 10M lines:
11:16cgrandreal 3m33.048s
11:16cgranduser 33m52.490s
11:16cgrandsys 0m53.788s
11:17rhickeycgrand: yes, I think hotspot sometimes optimized it away
11:18rhickeyare those good 10M line times?
11:20cgrandslightly worse than the imperative version I think (let me check)
11:20rhickeyhow many procs?
11:22cgrandproc usage is never precise -- only someone with root access could tell. (8 procs with 4 hardware threads)
11:31cgrandimperative on 10M:
11:31cgrandreal 3m11.918s
11:31cgranduser 32m35.173s
11:31cgrandsys 0m44.201s
11:41cgrandone lesson so far is to always run with -XX:+UseParallelOldGC on multiproc hardware without that full GCs runs only on one CPU and the others are sleeping
12:09blackdogwhat does this mean? Caused by: java.lang.Exception: Can't let qualified name
12:11blackdognevermind, it's in a macro, i was confoozed
16:12Lau_of_DKHey guys