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

cfbolz at codespeak.net cfbolz at codespeak.net
Sat Mar 24 13:29:55 CET 2007


Author: cfbolz
Date: Sat Mar 24 13:29:53 2007
New Revision: 41231

Modified:
   pypy/dist/pypy/doc/new-architecture.txt
Log:
mostly typo-level fixes


Modified: pypy/dist/pypy/doc/new-architecture.txt
==============================================================================
--- pypy/dist/pypy/doc/new-architecture.txt	(original)
+++ pypy/dist/pypy/doc/new-architecture.txt	Sat Mar 24 13:29:53 2007
@@ -13,7 +13,7 @@
 
 We aim to provide:
 
-* a common translation framework for generating interpreters
+* a common translation and support framework for generating interpreters
   and implementations of dynamic languages, supporting a clean separation 
   between language specification and implementation aspects. 
 
@@ -58,7 +58,7 @@
   a concrete interpreter for each target;
 
 * ``o``: tweak and optimize the translation process to produce 
-  platform specific code based on different models and tradeoffs.
+  platform specific code based on different models and trade-offs.
 
 * ``p``: write new translator back-ends to target 
   physical and virtual platforms;
@@ -89,7 +89,7 @@
 
 The architecture and abstractions of PyPy's "Python language specification" 
 aim to enable new implementation and optimization features that 
-tradtionally require pervasive changes in a language implementation 
+traditionally require pervasive changes in a language implementation 
 source code. 
 
 An important aspect of implementing Python in RPython is the high level of
@@ -100,7 +100,7 @@
 
 Another goal is to specify the language implementation in the form
 of a number of independent modules and abstractions, with clearly defined and 
-automatically tested API's.  This eases reuse and allows experimenting with 
+automatically tested APIs.  This eases reuse and allows experimenting with 
 variations and combinations of features. 
 
 Our Python language implementation architecture, however, also serves as a 
@@ -128,7 +128,7 @@
 The *Python Interpreter* is the subsystem implementing the Python language
 with the following key components: 
 
-- a bytecode compiler responsible for producing Python Code objects 
+- a bytecode compiler responsible for producing Python code objects 
 
 - a `bytecode evaluator`_ responsible for interpreting 
   Python code objects. 
@@ -169,7 +169,7 @@
 
 - the *annotator* which performs type inference on the flow graph;
 
-- the *typer* which, based on the type annotations, turns the flow graph
+- the *rtyper* which, based on the type annotations, turns the flow graph
   into another representation fitting the model of the target platform;
 
 - the *backend* which emits code for and integrates with the target platform. 
@@ -212,7 +212,7 @@
 require dealing with machine level types and pointers. 
 
 The actual target platform code is eventually emitted by 
-the backend through "visiting" the type-annontated flow graph
+the backend through "visiting" the type-annotated flow graph
 and adding platform specific integration code. 
 
 Here is a graphical overview of the translation process (`PDF color version`_):



More information about the Pypy-commit mailing list