The GC only gets crashy on multithreading if you have shared data ... that means: operate on BM data in C or have Callbacks
Otherwise its save to use threads.
The main point is that all stuff that runs in its own thread in C / C++ must be wrapped into a "manager". that manager is just an interface for BM to call. Like "eventwaiting()" and "retrieveevent" and the like. Those calls must run in the same thread as BM.
then you are out of problems.
by the way: just ordered a MacBook Pro Peryn based, so soon I'll be able to test that stuff on OSX as well :) (it will replace my old systems which are currently offered on ricardo)
Otherwise its save to use threads.
The main point is that all stuff that runs in its own thread in C / C++ must be wrapped into a "manager". that manager is just an interface for BM to call. Like "eventwaiting()" and "retrieveevent" and the like. Those calls must run in the same thread as BM.
then you are out of problems.
by the way: just ordered a MacBook Pro Peryn based, so soon I'll be able to test that stuff on OSX as well :) (it will replace my old systems which are currently offered on ricardo)