<html>
<head>
</head>
<body>
I think the really key difference is that stackless tasks are actually<br>
in the same operating system thread. The advantage of this is that<br>
it's a lot simpler to reason about (I hypothesize). The disadvantage<br>
is that if you have 64 CPU's the tasks are only using one of them<br>
at any given moment. Other than that I see no big theoretical difference<br>
In particular you can emulate locks, deadlocks shared memory etc.<br>
<br>
I don't like pthreads that much :(. Could be just my fear and ignorance.<br>
-- Aaron Watters<br>
<br>
Konrad Hinsen wrote:<br>
<blockquote type="cite" cite="mid:200302172027.09980.hinsen@cnrs-orleans.fr">
<pre wrap="">On Monday 17 February 2003 19:51, Russ Cox wrote:<br><br></pre>
<blockquote type="cite">
<pre wrap="">I disagree. Threading a la Stackless Python is<br>a good solution for putting concurrency into applications.<br>See <a class="moz-txt-link-freetext" href="http://plan9.bell-labs.com/~rsc/thread/">http://plan9.bell-labs.com/~rsc/thread/</a> for more<br>arguments to that effect.<br></pre>
</blockquote>
<pre wrap=""><!----><br>We need more terminology... I was thinking of threads as implemented in the <br>pthread library, with real parallelism, locks, deadlocks, and communication <br>via shared memory. The variant in Stackless Python is very different, based <br>on a system of synchronizing communication. I don't have enough experience <br>with it to have an opinion, but it sure is not the same as OS threads.<br><br>Konrad.<br><br>_______________________________________________<br>Stackless mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:Stackless@www.tismer.com">Stackless@www.tismer.com</a><br><a class="moz-txt-link-freetext" href="http://www.tismer.com/mailman/listinfo/stackless">http://www.tismer.com/mailman/listinfo/stackless</a><br><br></pre>
</blockquote>
<br>
</body>
</html>