[pypy-svn] r64221 - pypy/trunk/pypy/doc

antocuni at codespeak.net antocuni at codespeak.net
Fri Apr 17 10:54:29 CEST 2009


Author: antocuni
Date: Fri Apr 17 10:54:29 2009
New Revision: 64221

Modified:
   pypy/trunk/pypy/doc/cli-backend.txt
Log:
small updates to cli-backend.txt


Modified: pypy/trunk/pypy/doc/cli-backend.txt
==============================================================================
--- pypy/trunk/pypy/doc/cli-backend.txt	(original)
+++ pypy/trunk/pypy/doc/cli-backend.txt	Fri Apr 17 10:54:29 2009
@@ -63,11 +63,6 @@
   - directly generate code on the fly by accessing the facilities
     exposed by the System.Reflection.Emit API.
 
-The second point is not feasible yet because at the moment there is no
-support for accessing system libraries, but in future it could lead to
-an interesting GenCLI feature, i.e. the ability of emitting dynamic
-code at runtime.
-
 
 Handling platform differences
 =============================
@@ -124,7 +119,7 @@
 Mapping primitive types
 -----------------------
 
-The `rtyper` give us a flow graph annotated with types belonging to
+The `rtyper`_ give us a flow graph annotated with types belonging to
 ootypesystem: in order to produce CLI code we need to translate these
 types into their Common Type System equivalents.
 
@@ -268,7 +263,7 @@
 Translating flow graphs
 -----------------------
 
-As we saw previously in PyPy\ function and method bodies are
+As we saw previously in PyPy function and method bodies are
 represented by flow graphs that we need to translate CLI IL code. Flow
 graphs are expressed in a format that is very suitable for being
 translated to low level code, so that phase is quite straightforward,
@@ -312,7 +307,7 @@
       # block2
       ...
 
-    // IL
+  // IL
   block0: 
     .try {
         ...
@@ -344,11 +339,11 @@
 Translating classes
 -------------------
 
-As we saw in section sec:ootypes, the semantic of ootypesystem classes
+As we saw previously, the semantic of ootypesystem classes
 is very similar to the .NET one, so the translation is mostly
 straightforward.
 
-The related code is located in the module class\_.py.  Rendered classes
+The related code is located in the module class_.py.  Rendered classes
 are composed of four parts:
 
   - fields;
@@ -444,7 +439,7 @@
 for .NET; the only version tested with PyPy is the 1.0-rc2, but it
 might work also with others. Then, you need to create a file named
 Python.Runtime.dll.config at the root of the unpacked archive; put the
-following lines inside the file::
+following lines inside the file (assuming you are using Python 2.4)::
 
   <configuration>
     <dllmap dll="python24" target="libpython2.4.so.1.0" os="!windows"/>



More information about the Pypy-commit mailing list