Multithreaded Irrlicht

[hybrid]

For cross-platform OO threading I used ZThread once. It's rather simple but works for the common cases.
For communication you can use shared variables because you have a common process space. Why would you want to use such complex things?

[rogerborg]

ZThreads looks reasonable. It's MIT licensed, so could just be incorporated into Irrlicht as-is. The problem with becoming reliant on it (or on multithreading in general) is that it's Posix and Win32 only, which might scupper attempts to port Irrlicht to (e.g.) Symbian or BREW.

[hybrid]

Maybe Niko will provide IrrThreads But otherwise it's better to have the most common systems already covered!

[Legion]

True forking is NOT threading, when you fork you clone the process,
splitting it into two independant address spaces.
vfork on the otherhand won't duplicate the memory pages and can
be used, but it's not recommended.
Basicly all unix systems i've come accross supports pthreads,
if they are somewhat posix compliant.
Infact i've never seen a unix system(true or clone) that doesn't have pthreads.
(very very old systems might lack pthreads, but they probably lack graphics too...)
Since it's part of the posix threads extensions standard.

[zenaku]

This is what OpenAL++ uses.

http://openthreads.sourceforge.net/


Small, C++, cross platform (win32 & linux supported), LGPL v2.


The API is fairly straight forward.