2012/1/15 john skaller <[email protected]>: > There's also an issue with atomicity (is that a word?). > Doing something THEN fetching the result in a separate operation > is dangerous. What happens if there's a context switch in between? > > OK, so it can't be a pthread .. but what about a signal, or, in my case, > a Felix f-thread (fibre)... the errno value would be corrupted. > Windows has fibres too. The problem is even more obvious with bytecode > interpreters like Python where you potentially have context switches > every instruction, potentially cooperative.
I've just checked source code of CRT library in Visual Studio 2010 SP1 and in Visual Studio 2008 SP1: errno is fiber-local both in 32-bit and in 64-bit builds. _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
