14.08.2012 16:19, Stas Sergeev пишет: > > Maybe we should just call them coroutines, as that's what the C in > PCL stands for, and as threads confuse me into thinking they run in > parallel.
> 2. If libpcl already implements co-routines, then what > my code does? Oh, but it does cooperative threading! > Good term for marketing. :)) Actually, this is not just a marketing term, I really think coopthreads is the right name. The main difference with coroutines is that my API is not for the explicit switching. Its all about the scheduling: the main dosemu thread cannot switch to any other thread. It can only create thread (which just creates the coroutine, yes), but it can't switch there, it have to exit. The switching will be done later by the DOS code (via the hlt handler). The secondary thread can switch explicitly, but only back to the scheduler, which, depending on why it have switched there, will do different things. So really this is a coopthreading, not coroutines. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
