2009/10/21 Doug Coleman <[email protected]>: > I think it makes sense to totally separate out all of the new > threading from the green threads implementation like we do for native/ > libc io so we can bootstrap with either one until all of the issues > are resolved. The current API can probably be a starting point, but I > think the implementation will have to completely change for native > threads.
Excuse me butting in, but while I'm not familiar with how the threading work is progressing, I am nevertheless interested in it. >From the sound of this, the new threading implementation will replace the existing one. Is that correct? I wasn't aware that was the plan - I had (maybe naively) assumed that the existing threading would remain for those places where it is appropriate, while OS threading would be available via a separate vocabulary. This seems sensible to me, as I assume that OS threading is likely to be heavier weight than green threads, and so should only be used where needed. If there's anywhere I can read up on the higher level plans for threading (as opposed to Phil's postings on the lower-level details, which I've read with interest), could someone point me there? Thanks, Paul. ------------------------------------------------------------------------------ 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
