[m-dev.] thread.spawn_native

Michael Day mikeday at yeslogic.com
Tue Jun 10 18:15:33 AEST 2014


> That is, there could be separate classes of Mercury engines if
> necessary.  A fixed number of "parallel execution workers" created at
> startup, but also other Mercury engines created explicitly by
> thread.spawn_native.

I really like this idea. Having some control over low-level threading 
would be very helpful. (In fairness, I don't understand the current 
parallel execution mechanism at all).

Cheers,

Michael

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



More information about the developers mailing list