Author: Armin Rigo <[email protected]> Branch: extradoc Changeset: r4027:2053ec4541aa Date: 2012-01-13 15:31 +0100 http://bitbucket.org/pypy/extradoc/changeset/2053ec4541aa/
Log: tweak diff --git a/blog/draft/tm.rst b/blog/draft/tm.rst --- a/blog/draft/tm.rst +++ b/blog/draft/tm.rst @@ -102,7 +102,8 @@ Events might also be *mostly independent*, i.e. they rarely access the same object concurrently. Of course, in a multi-threaded world we would still need a lock to ensure correctness, but the point is that without the lock the -program would run correctly "most of the time". +program would run correctly "most of the time" (and likely segfault the rest +of the time). Consider again the Twisted example I gave above. There are often several events pending in the dispatch queue (assuming the program is using 100% _______________________________________________ pypy-commit mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-commit
