Matt wrote this nice patch to add condition-variables for LispWorks, and I never  got it merged. I'm gone for the weekend, then switching jobs next week, then gone in Pittsburgh, then to Europe. I'm afraid if it's left to me, this will never get in.

The only thing from my perspective that should change is that the unit-test-lw-conditions function should be moved into the test suite (as it should work just fine for any impl) so everyone gets the benefit. Stelian has a much better view of the state of BT these days than I do.

Begin forwarded message:

From: "Matthew Lamari" <matt.lamari@gmail.com>
Date: 3 June 2008 11:55:42 EDT
To: "Greg Pfeil" <greg@technomadic.org>
Subject: Re: [Bordeaux-threads-devel] Lispworks additions to Bordeaux - where do I submit?


I'm a win32 guy, so I'm not sure what you'd want the file diffed with - please find the full file enclosed - I'm guessing the original doesn't change very often, and that you could diff it faster than explaining to me what to do.
 
I added a simple unit-test and tried to heavily comment this, as it's not trivial like the other call-throughs, and should probably come under more scrutiny.
 
(Unlike the non-implementation-supported literal polling) the Lispworks' "process-wait"-based polling seems lightweight enough to be usable in the same situations as true condition/notification, with negligible cpu hit while waiting (see my comments if interested).