Fair enough; I was not complaining so much as pointing out that the exact manner in which Haskell threads interact with the FFI is not "obvious" (as you described it) given that the documentation is confusing. Should I file a bug report to request that the documentation be updated? Cheers, Greg On 8/5/10 7:52 AM, Brandon S Allbery KF8NH wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 8/5/10 00:47 , Gregory Crosswhite wrote:
The documentation is a little confusing on this issue. It sounded to me when I read the documentation that all of the *OS* threads were blocked by the FFI, when what was meant was that all of the *IO* threads assigned to the calling OS thread are what is blocked, because the docs just say that "threads" are blocked without being clear that they are only referring to a particular subset of the threads. To be fair, until relatively recently (6.8? 6.6?) there wasn't a difference; the docs are out of date, not incomplete.
- -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxa0C0ACgkQIn7hlCsL25V+xACgoINpPvqWAsXXfqJqN8PfjzCw NVMAoNbCMShzmm8mi8T8niWy18pLanJu =G9AH -----END PGP SIGNATURE----- _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe