Hi Slava,

I've written initial os-thread mutex and semaphore FFIs in 
extra:concurrency.locks.unix and concurrency.locks.windows, and was just 
about to wrap it together into a unified api when I realised 
concurrency.locks was already used for cooperative threads.

- Should there be a totally separate concurrency package for os threads?

- From an API perspective do you plan to distinguish between cooperative 
and os-threads in the brave new factorMT world?

Cheers,

Phil


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk

Reply via email to