bordeaux-threads-devel

Download

bordeaux-threads-devel@common-lisp.net

June 2007

3 participants
2 discussions

[Bordeaux-threads-devel] [PATCH] Mark more Lisp implementations as unsupported
by Thiemo Seufer 25 Jun '07

25 Jun '07

Hello All, the appended patch stops bordeaux-threads from compiling successfully for Lisp implementations which have no threading support enabled. Thiemo --- bordeaux-threads/src/allegro-orig.lisp 2006-06-06 03:44:26.000000000 +0100 +++ bordeaux-threads/src/allegro.lisp 2007-06-24 12:13:40.000000000 +0100 @@ -75,3 +75,6 @@ (mp:process-kill thread)) ) ; end PROGN + +#-multiprocessing +(error "This implementation of ALLEGRO does not support threads.") --- bordeaux-threads/src/cmu-orig.lisp 2007-06-24 11:16:38.000000000 +0100 +++ bordeaux-threads/src/cmu.lisp 2007-06-24 12:13:58.000000000 +0100 @@ -84,3 +84,6 @@ (mp:destroy-process thread)) ) ; end PROGN + +#-mp +(error "This implementation of CMUCL does not support threads.") --- bordeaux-threads/src/sbcl-orig.lisp 2007-06-24 10:46:12.000000000 +0100 +++ bordeaux-threads/src/sbcl.lisp 2007-06-24 12:13:58.000000000 +0100 @@ -74,3 +74,6 @@ (sb-thread:terminate-thread thread)) ) ; end PROGN + +#-sb-thread +(error "This implementation of SBCL does not support threads.") --- bordeaux-threads/src/openmcl-orig.lisp 2006-06-06 03:44:26.000000000 +0100 +++ bordeaux-threads/src/openmcl.lisp 2007-06-24 12:14:14.000000000 +0100 @@ -83,4 +83,7 @@ (defmethod destroy-thread ((thread ccl:process)) (ccl:process-kill thread)) -) ; end PROGN \ No newline at end of file +) ; end PROGN + +#-openmcl-native-threads +(error "This implementation of OpenMCL does not support threads.")

1 0

[Bordeaux-threads-devel] send/receive message api
by Attila Lendvai 05 Jun '07

05 Jun '07

hi! i'm about to implement a simple send/receive message api based on condition variables and i wonder whether it fits the scope of bordeaux-threads... if you also think it does, then let me know and i'll send a patch. another thing i'm missing and which is not strictly a primitive is a read/write lock (even if it's a naiive implementation). i know that these features are implementable in terms of the current b-t api (i'm not sure about the read/write lock, though), but where else would we put them then a threading lib? -- attila

2 2