Hi all,
is it ok to do a wild guess?
thread-terminate! looks suspicious here in comparsion to other uses of
thread's slot #2:
$ svn diff srfi-18.scm
Index: srfi-18.scm
===================================================================
--- srfi-18.scm (Revision 11547)
+++ srfi-18.scm (Arbeitskopie)
@@ -259,7 +259,7 @@
(##sys#check-structure thread 'thread 'thread-terminate!)
(when (eq? thread ##sys#primordial-thread)
((##sys#exit-handler)) )
- (##sys#setislot thread 2 (list (##core#undefined)))
+ (##sys#setslot thread 2 (list (##core#undefined)))
(##sys#setslot thread 7 (##sys#make-structure 'condition
'(terminated-thread-exception) '()))
(##sys#thread-kill! thread 'terminated)
(when (eq? thread ##sys#current-thread) (##sys#schedule)) )
I patched it as above and the testcases I posted yesterday and the day
before are working now in my environment.
Am I correct, that setislot will set immediate values, while a list
clearly in not?
Best regards
/Jörg
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
