[m-dev.] thread.spawn_native

[Michael Day]

Hi Paul,

Thinking about it some more, without thread pinning, I don't see the 
point of having spawn_native at all. Couldn't you just call spawn and 
use may_not_migrate annotations? And adjust the number of Mercury 
engines at startup to the desired number?

Unless I've got it completely backwards, it seems like the whole point 
of spawn_native is to give you guaranteed control over a native thread, 
deliberately breaking the abstraction barrier that would normally be 
imposed between Mercury code and and the operating system.

Michael

-- 
Prince: Print with CSS!
http://www.princexml.com