14:42:32thijsoThe 'attempted to recursively lock..' error seems to be gone, indeed, but I still get the 'Condition of type: UNKNOWN-ERROR' at the start in the udp processing thread, Shinmera... Looks like I'll need to do some debugging there
14:43:48ShinmeraI don't know what that's about, so I can't help you there.
14:44:01thijsoThe error message with that one is: "The condition Not a condition type: NIL occurred with errno: 0." Somehow the udp thread is getting signalled with a condition NIL? Is that how I need to read that error?
14:45:05thijsoJust weird that it crops up only if I include verbose as a dependency. Even without calling any code in there. But I think it always starts up threads, right? Is there a way to turn that off?
17:56:48tfbhortiel: when reading data (which is the same as when reading code) #n= (where n is an integer) makes a 'label' for something being read, and #n# refers to that label. This means self-referential (circular) objects can be read.
18:02:15moldybits#1=42 is the same as 42 except you can now refer to 42 with #1#, but only within the same "read context" or something like that.