[pypy-svn] r55731 - pypy/dist/pypy/doc

[arigo at codespeak.net]

Author: arigo
Date: Tue Jun 10 12:10:59 2008
New Revision: 55731

Modified:
   pypy/dist/pypy/doc/translation.txt
Log:
Update.


Modified: pypy/dist/pypy/doc/translation.txt
==============================================================================
--- pypy/dist/pypy/doc/translation.txt	(original)
+++ pypy/dist/pypy/doc/translation.txt	Tue Jun 10 12:10:59 2008
@@ -644,19 +644,16 @@
 must be made.  In keeping with PyPy's approach to flexibility, there is
 freedom to change how to do it.  There are three approaches implemented today:
 
- - reference counting
+ - reference counting (deprecated, too slow)
  - using the `Boehm-Demers-Weiser conservative garbage collector`_
- - using a mark and sweep collector implemented in RPython
+ - using one of our custom `exact GCs implemented in RPython`_
 
 .. _`Boehm-Demers-Weiser conservative garbage collector`: http://www.hpl.hp.com/personal/Hans_Boehm/gc/
+.. _`exact GCs implemented in RPython`: garbage_collection.html
 
 Almost all application-level Python code allocates objects at a very fast
-rate; this means that the memory management implementation is critical too the
-performance of the PyPy interpreter.  That said, work so far has many focussed
-on flexibility and robustness, not performance.
-
-For a quite detailed description of how memory management and garbage collection
-are performed in PyPy, see the `Technical report`_ about this topic (section 4.2).
+rate; this means that the memory management implementation is critical to the
+performance of the PyPy interpreter.
 
 You can choose which garbage collection strategy to use with
 :config:`translation.gc`.