freenode/#sbcl - IRC Chatlog
Search
22:31:34
pfdietz
67 internal symbols referenced in QL systems do not actually exist in current SBCL (cause package lock violation when I try to read them).
22:36:28
pfdietz
Hmm. Many references to symbols use :: when the symbol is actually external to its home package.
22:53:55
stassats
(defun foo () (block nil (sb-thread:make-thread (lambda () (return))))) => (foo) i can now find the name of FOO
23:25:53
AeroNotix
stassats: %emit-skip seems undefined, even when accessing via :: and unlocking packages. Why is that?
23:27:38
rbarraud
I'm about to prove that for myself... not too far off [OT Trigger warning!11!!] writing my first for my B0rgScheme (soon-to-be-native-metal-x64 hopefully-R7RS Scheme) :-)
23:32:34
rbarraud
Weirdly though, I may be about to move even more southward... maybe like 850 miles / 1400km South...
23:33:39
AeroNotix
stassats: so what's the bigger picture with coming up with a stable API for things like sb-assem, sb-vm etc?
23:33:57
AeroNotix
judging by what's been accomplished with stmx (if it works, I've never used it until today)
23:40:03
AeroNotix
for CL testing in general, you should ask in #lisp for a better answer but I really like rove or prove, but avoid fiveam :)
23:43:07
AeroNotix
oh the whole reason I was looking at stmx was that, couldn't it be possible to use an stm implementation to change how the timer scheduler works in SBCL? As far as I understand it, the timer module has a single threaded scheduler that is woken up every period, locks its timer queue, walks the queue and triggers any timers. The issue being that each invocation of the timer still requires that the timer scheduler
23:43:24
AeroNotix
from reading the implementation the locking is done to prevent multiple threads from accessing the timer queue and adding/removing timers.
23:43:52
AeroNotix
With an STM implementation instead of locks (optimistic concurrency) the scheduler thread and the user threads require no locking
23:45:12
AeroNotix
stassats: no but they make using it a little irksome, hence my questions/issues the other night about unscheduling timer functions that are currently running blocking until the scheduled function has completed
23:50:54
AeroNotix
It's very cool that stmx can even work to begin with and present the API like it does