2:15cgrand: then Clojure won't help you -- except if you break your app in two: client and server (which only purpose would be to handle writes to the xml file send from the clients)

2:48Lau_of_DK: Thats what I figured - I wondered if thats really complicated though :)

9:09cemerick: I'm just now looking at lib.clj -- having a couple of issues, though. (a) isn't require supposed to fail if it can't load a library, and (b) what's the correct incantation to get require/use to grab a library from a package? I have foo.clj in com/pkg, and none of these seem to work: (use com.pkg.foo) (use "com.pkg.foo") (use 'com.pkg.foo), etc.

10:00 is there a docstring convention for clojure and/or a help function to read them?

10:00rhickey: spacebat_: sure - stick with it, and especially look into refs and transactions. Clojure is actually for solving the problems one solves with C#/Java. It supports functional programming _and_ sane state

10:02spacebat_: when I mention the properties of clojure to some people, they sometimes mention erlang

10:02 I guess with the right libs that sort of distributed fault tolerant concurrency would be in easy reach

10:03rhickey: Clojure currently only addresses the non-distributed case

10:04spacebat_: yes, and distributing things is probably best left to the libs

10:07scgilardi: rhickey: currently loadResourceScript silently fails if the resource doesn't exist. I would prefer it to either throw an exception or return an indication of failure. Would you consider that?

10:12rhickey: scgilardi: yes, something, either taking a flag indicating throw if not found or a return value. Unconditional throw is out, as I use it for speculative reads and don't like EH for flow control

16:01 I'm seeing (old) examples that include hints like #^float, but using such things yields an exception (class not found). The primitives section only lists hints for primitive arrays; has simple primitive hinting changed, or gone away?