Author: Armin Rigo <[email protected]> Branch: extradoc Changeset: r5454:44f5129e47c6 Date: 2014-11-05 10:21 +0100 http://bitbucket.org/pypy/extradoc/changeset/44f5129e47c6/
Log: tweaks diff --git a/blog/draft/io-improvements.rst b/blog/draft/io-improvements.rst --- a/blog/draft/io-improvements.rst +++ b/blog/draft/io-improvements.rst @@ -31,8 +31,8 @@ time to time moves the objects in memory, meaning that their address can change. Therefore, if you want to pass pointers to some external C function (for example, write(2) or read(2)), you need to ensure that the objects they are -pointing to will not be moved by the GC. -PyPy 2.4 solves the problem by copying the data into a non-movable buffer, which +pointing to will not be moved by the GC (e.g. when running a different thread). +PyPy up to 2.4 solves the problem by copying the data into or from a non-movable buffer, which is obviously inefficient. The branch introduce the concept of "pinning", which allows us to inform the GC that it is not allowed to move a certain object for a short period of time. _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
