On Sat, Jul 5, 2008 at 2:24 AM, Elliott Slaughter
> which I am similarly stumped by. I am tempted to just wrap these and
> other similar instances with "#ifndef LISP_FEATURE_WIN32" but I am not
> sure if I need to implement equivalent code for win32 or not.
Depends on how thread stacks will work on Windows. The post mortem
stuff is there to deal with freeing thread stacks after the thread has
You can #ifdef if out for now, and later, when you know if you need it
or not, you can deal with it appropriately.
As for various pthread_foo functions and types:
* In those cases where there is a Windows equivalent (not maybe 1:1,
but something sufficiently close) hiding the difference under
os_thread_foo functions and types is the right thing.
* If there is no Windows equivalent, then those definitions can be
empty -- it probably makes the code easier to read in the long run the
adding #ifndef LISP_FEATURE_WIN32 around them.
* ...the hard case is when there is a Windows equivalent you need to
use, but which is sufficiently different from the pthreads version
that providing a single interface to both is a non-starter: then you
just have work case-by-case.