[pypy-svn] r29207 - pypy/dist/pypy/doc
ericvrp at codespeak.net
ericvrp at codespeak.net
Fri Jun 23 11:57:17 CEST 2006
Author: ericvrp
Date: Fri Jun 23 11:57:16 2006
New Revision: 29207
Modified:
pypy/dist/pypy/doc/glossary.txt
Log:
Removed content listing at top of glossary and
changed layout.
Modified: pypy/dist/pypy/doc/glossary.txt
==============================================================================
--- pypy/dist/pypy/doc/glossary.txt (original)
+++ pypy/dist/pypy/doc/glossary.txt Fri Jun 23 11:57:16 2006
@@ -1,173 +1,91 @@
-==========================
-PyPy - Glossary
-==========================
+**annotator** - Performs a form of `type inference`_ on the flow graph.
-.. contents::
+**application level** - applevel_ code is normal Python code running on
+top of the PyPy or CPython interpreter (See interpreter level)
+.. _backend:
-annotator
-----------------------------------------------------------------------
+**backend** - Code generator that convert a RPython_ program to a
+`target language`_ using the PyPy toolchain_. A backend uses either the
+lltypesystem_ or the ootypesystem_.
-Performs a form of `type inference`_ on the flow graph.
+**external function** - Functions that we don't want to implement in Python
+for various reasons (e.g. if they need to make calls into the OS) and will
+be implemented by the backend.
+**garbage collection framework** - Code that makes it possible to write
+`PyPy's garbage collectors`_ in Python itself.
-application level
---------------------------------------------
+.. _`interpreter level`:
-applevel_ code is normal Python code running on top of the PyPy or
-CPython interpreter
+**interpreter level** - Code running at this level is part of the
+implementation of the PyPy interpreter and cannot interact normally with
+application level code; it typically provides implementation for an object
+space and its builtins. (See application level)
-See interpreter level
+**jit** - `just in time compiler`_
-backend
-----------------------------------------------------------------------
+**l3interpreter** - Piece of code that is able to interpret L3 flow graphs.
+This code is unfinished and its future is unclear.
-Code generator that convert a RPython_ program to a `target language`_ using
-the PyPy toolchain_. A backend uses either the lltypesystem_ or the ootypesystem_.
+**llinterpreter** - Piece of code that is able to interpret flow graphs.
+This is very useful for testing purposes, especially if you work on the
+RPython_ Typer.
+.. _lltypesystem:
-external function
-----------------------------------------------------------------------
+**lltypesystem** - A backend_ that uses this typessystem is also called a
+low-level backend. The C and LLVM backends are using this typesystem.
-Functions that we don't want to implement in Python for various reasons
-(e.g. if they need to make calls into the OS) and will be implemented by the backend.
+**mixed module** - a module that accesses PyPy's `interpreter level`_
+**object space** - The `object space`_ creates all objects and knows how to
+perform operations on the objects. You may think of an object space as being
+a library offering a fixed API, a set of operations, with implementations
+that a) correspond to the known semantics of Python objects, b) extend or
+twist these semantics, or c) serve whole-program analysis purposes.
-garbage collection framework
---------------------------------------------
+.. _ootypesystem:
-Code that makes it possible to write `PyPy's garbage collectors`_ in Python
-itself.
+**ootypesystem** - A backend_ that uses this typessystem is also called a
+high-level backend. The common lisp, javascript and cli backends are all
+using this typesystem.
+**prebuilt constant** - In RPython_ module globals are considered constants.
+Moreover, global (i.e. prebuilt) lists and dictionaries are supposed to be
+immutable. (prebuilts are sometimes called pbc's)
-interpreter level
---------------------------------------------
+**rpython** - `Restricted Python`_, which is the limited subset of the
+Python_ specification. It is also the language that the PyPy interpreter
+itself is written in.
-Code running at this level is part of the implementation of the PyPy
-interpreter and cannot interact normally with application level code;
-it typically provides implementation for an object space and its
-builtins.
+**rtyper** - Based on the type annotations, the `RPython Typer`_ turns the
+flow graph into one that fits the model of the target platform/backend_ using
+either the lltypesystem_ or the ootypesystem_.
-See application level.
+**specialization** - XXX
+**stackless** - Technology that enables various forms of coroutining.
-jit
---------------------------------------------
+**standard interpreter** - It is the
+`subsystem implementing the Python language`_, composed of the bytecode
+interpreter and of the standard objectspace.
-`just in time compiler`_
+.. _toolchain:
+**toolchain** - The `annotator pass`_, `The RPython Typer`_, and various
+`backends`_.
-l3interpreter
-----------------------------------------------------------------------
+**transformation** - Code that modifies flowgraphs to weave in
+`translation-aspects`_
-Piece of code that is able to interpret L3 flow graphs. This code is
-unfinished and its future is unclear.
+**translator** - Tool_ based on the PyPy interpreter which can translate
+sufficiently static Python programs into low-level code.
+.. _`type inference`:
-llinterpreter
-----------------------------------------------------------------------
-
-Piece of code that is able to interpret flow graphs. This is very useful for
-testing purposes, especially if you work on the RPython_ Typer.
-
-
-lltypesystem
-----------------------------------------------------------------------
-
-A backend_ that uses this typessystem is also called a low-level backend.
-The C and LLVM backends are using this typesystem.
-
-
-mixed module
-----------------------------------------------------------------------
-
-a module that accesses PyPy's `interpreter level`_
-
-
-object space
-----------------------------------------------------------------------
-
-The `object space`_ creates all objects and knows how to perform
-operations on the objects. You may think of an object space as being a
-library offering a fixed API, a set of operations, with
-implementations that a) correspond to the known semantics of Python
-objects, b) extend or twist these semantics, or c) serve
-whole-program analysis purposes.
-
-
-ootypesystem
-----------------------------------------------------------------------
-
-A backend_ that uses this typessystem is also called a high-level backend.
-The common lisp, javascript and cli backends are all using this typesystem.
-
-
-prebuilt constant
---------------------------------------------
-In RPython_ module globals are considered constants. Moreover, global
-(i.e. prebuilt) lists and dictionaries are supposed to be immutable.
-(prebuilts are sometimes called pbc's)
-
-
-rpython
---------------------------------------------
-
-`Restricted Python`_, which is the limited subset of the
-Python_ specification. It is also the language that the PyPy
-interpreter itself is written in.
-
-
-rtyper
---------------------------------------------
-
-Based on the type annotations, the `RPython Typer`_ turns the flow graph into one that fits the
-model of the target platform/backend_ using either the lltypesystem_ or
-the ootypesystem_.
-
-
-specialization
---------------------------------------------
-
-XXX
-
-
-stackless
-----------------------------------------------------------------------
-
-Technology that enables various forms of coroutining.
-
-
-standard interpreter
---------------------------------------------
-
-It is the `subsystem implementing the Python language`_, composed of the
-bytecode interpreter and of the standard objectspace.
-
-toolchain
-----------------------------------------------------------------------
-
-The `annotator pass`_, `The RPython Typer`_, and various `backends`_.
-
-
-transformation
-----------------------------------------------------------------------
-
-Code that modifies flowgraphs to weave in `translation-aspects`_
-
-
-translator
-----------------------------------------------------------------------
-
-Tool_ based on the PyPy interpreter which can translate sufficiently static
-Python programs into low-level code.
-
-
-type inference
-----------------------------------------------------------------------
-
-Deduces either partially or fully the type of expressions as described in
-this `type inference article`_.
-
+**type inference** - Deduces either partially or fully the type of
+expressions as described in this `type inference article`_.
.. _applevel: coding-guide.html#application-level
More information about the Pypy-commit
mailing list