Author: Wouter van Heyst <[email protected]> Branch: extradoc Changeset: r340:3928f55afd97 Date: 2012-03-08 15:51 +0200 http://bitbucket.org/pypy/pypy.org/changeset/3928f55afd97/
Log: Fix some typos in source/tmdonate.txt. diff --git a/source/tmdonate.txt b/source/tmdonate.txt --- a/source/tmdonate.txt +++ b/source/tmdonate.txt @@ -27,7 +27,7 @@ This proposal is about researching and implementing Transactional Memory in PyPy. This is a technique that recently came to the front of the -multi-core scene. It promizes to offer multi-core CPU usage without +multi-core scene. It promises to offer multi-core CPU usage without requiring to fall back to the multi-process solutions described above, and also without using the ``threading`` module --- just as a small, local extension of the programming language that would be used only in @@ -124,7 +124,7 @@ -------------------------------- This is a classic criticism of research-oriented projects. We believe -that the `work plan`_ plan below can make a serious impact on considering +that the `work plan`_ below can make a serious impact on considering possible a GIL-less Python. We believe we can do it, but at the very least, even if this work generates a negative result, the negative result will document the challenges faced should someone else want to @@ -255,7 +255,7 @@ alternatives. In particular, small quickly-written programs don't need the additional baggage of cross-process communication, and large programs can sometimes be almost impossible to turn into multi-process -versions. By constrast, we believe that TM can fit naturally into most +versions. By contrast, we believe that TM can fit naturally into most programs, because it only requires local changes to some dispatcher; the rest of the program should work without changes. _______________________________________________ pypy-commit mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-commit
