Author: Maciej Fijalkowski <[email protected]> Branch: extradoc Changeset: r5080:94b857d4e394 Date: 2013-10-15 10:31 +0200 http://bitbucket.org/pypy/extradoc/changeset/94b857d4e394/
Log: a clarification diff --git a/blog/draft/incremental-gc.rst b/blog/draft/incremental-gc.rst --- a/blog/draft/incremental-gc.rst +++ b/blog/draft/incremental-gc.rst @@ -165,7 +165,7 @@ The trick we used in PyPy is to consider minor collections as part of the whole, rather than focus only on major collections. The existing minimark GC had always used a "write barrier" (a piece of code run every time -you set or get from an object or array) to do its job, like any +you set or get a pointer from an object or array) to do its job, like any generational GC. This write barrier is used to detect when an old object (outside the nursery) is modified to point to a young object (inside the nursery), which is essential information for minor _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
