Clojurians Log v2

Two questions about planck: - It adds the current working dir + the src folder on the default classpath, is that correct? - If you are adding a bunch of jars to the classpath and you do a require, does it walk through the list and searches for entries in each jar file until it found the correct entry, every time you do a require for a previously unloaded namespace? Or does it have some sort of caching about what file belongs to which jar file? I briefly skimmed through the C code: it seems the former. I'm asking because I'm considering similar --classpath option for for babashka and want to have some information about best practices.

@borkdude If I recall correctly, Planck itself doesn't actually cache JAR entries, but there is evidence that the underlying library is faster if the archives are left open: https://github.com/planck-repl/planck/issues/566

For your first question, raw planck doesn't add anything to the classpath, but plk behaves like clj.

I get:

$ plk -e "(require '[foo]) (require '[bar])"
WARNING: foo is a single segment namespace at line 1
foo
WARNING: bar is a single segment namespace at line 1 /private/tmp/src/bar.cljs
bar

CWD I mean

maybe that's true

For babashka the same would make sense I think

(also putting the cwd on the classpath)

I think I had Planck originally doing that, and perhaps just left it as is so as to not break anything.

for bash-like scripting I think that makes sense, just put everything in one dir

@mfikes fwiw clj-kondo had a weird issue which was caused by keeping jar files open: https://github.com/borkdude/clj-kondo/issues/542 it hit the OS limit for open files for some people who had a huge list of dependencies on their classpath