[pypy-commit] pypy improve-docs: Fix references and remove all mentions of the 'flow object space'

[rlamy]

Author: Ronan Lamy <ronan.lamy at gmail.com>
Branch: improve-docs
Changeset: r74163:8f892834785a
Date: 2014-10-24 14:38 +0200
http://bitbucket.org/pypy/pypy/changeset/8f892834785a/

Log:	Fix references and remove all mentions of the 'flow object space'

diff --git a/rpython/doc/architecture.rst b/rpython/doc/architecture.rst
--- a/rpython/doc/architecture.rst
+++ b/rpython/doc/architecture.rst
@@ -74,7 +74,7 @@
 The steps of the translation process can be summarized as follows:
 
 * The code object of each source functions is converted to a :ref:`control
-  flow graph <flow-model>` by the :ref:`Flow Object Space <flow-object-space>`.
+  flow graph <flow-model>` by the :ref:`flow graph builder<flow-graphs>`.
 
 * The control flow graphs are processed by the :ref:`Annotator <annotator>`, which
   performs whole-program type inference to annotate each variable of
diff --git a/rpython/doc/dir-reference.rst b/rpython/doc/dir-reference.rst
--- a/rpython/doc/dir-reference.rst
+++ b/rpython/doc/dir-reference.rst
@@ -12,20 +12,17 @@
 
 :source:`rpython/config/`                 handles the numerous options for RPython
 
-:source:`rpython/flowspace/`              the :ref:`FlowObjSpace_ <flow-object-space>` implementing
+:source:`rpython/flowspace/`              the :ref:`flow graph builder<flow-graphs>` implementing
                                           `abstract interpretation`_
 
 :source:`rpython/rlib/`                   a :doc:`"standard library" <rlib>` for :doc:`RPython <rpython>`
                                           programs
 
-:source:`rpython/rtyper/`                 the :ref:`RPython Typer <rpython-typer>`
+:source:`rpython/rtyper/`                 the :ref:`RPython Typer <rtyper>`
 
 :source:`rpython/rtyper/lltypesystem/`    the :ref:`low-level type system <low-level-types>` for
                                           C-like backends
 
-:source:`rpython/rtyper/ootypesystem/`    the :ref:`object-oriented type system <oo-type>`
-                                          for OO backends
-
 :source:`rpython/memory/`                 the :doc:`garbage collector <garbage_collection>` construction
                                           framework
 
diff --git a/rpython/doc/rlib.rst b/rpython/doc/rlib.rst
--- a/rpython/doc/rlib.rst
+++ b/rpython/doc/rlib.rst
@@ -28,7 +28,7 @@
 nonconst
 --------
 
-The :source:`rpython/rlib/nonconst.py` module is useful mostly for tests. The :ref:`flow object space <flow-object-space>` and
+The :source:`rpython/rlib/nonconst.py` module is useful mostly for tests. The :ref:`flow graph builder<flow-graphs>` and
 the :ref:`annotator <annotator>` do quite some constant folding, which is sometimes not desired
 in a test. To prevent constant folding on a certain value, use the ``NonConst``
 class. The constructor of ``NonConst`` takes an arbitrary value. The instance of
diff --git a/rpython/doc/translation.rst b/rpython/doc/translation.rst
--- a/rpython/doc/translation.rst
+++ b/rpython/doc/translation.rst
@@ -30,12 +30,10 @@
 
 .. _initialization-time:
 
-.. TODO edit information about flow object space
-
 The RPython translation toolchain never sees Python source code or syntax
 trees, but rather starts with the *code objects* that define the
 behaviour of the function objects one gives it as input.  The
-`bytecode evaluator`_ and the :ref:`Flow Object Space <flow-object-space>` work through these
+`bytecode evaluator`_ and the :ref:`flow graph builder<flow-graphs>` work through these
 code objects using `abstract interpretation`_ to produce a control
 flow graph (one per function): yet another representation of the
 source program, but one which is suitable for applying type inference
@@ -52,8 +50,8 @@
 
 2. The Annotator_ performs a global analysis starting from an specified
    entry point to deduce type and other information about what each
-   variable can contain at run-time, building flow graphs using the
-   :ref:`Flow Object Space <flow-object-space>` as it encounters them.
+   variable can contain at run-time, :ref:`building flow graphs <flow-graphs>`
+   as it encounters them.
 
 3. The :ref:`RPython Typer <rtyper>` (or RTyper) uses the high-level
    information inferred by the Annotator to turn the operations in the control