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

arigo at codespeak.net arigo at codespeak.net
Mon Sep 12 17:47:06 CEST 2005


Author: arigo
Date: Mon Sep 12 17:47:04 2005
New Revision: 17507

Modified:
   pypy/dist/pypy/doc/draft-dynamic-language-translation.txt
Log:
Added a sentence...


Modified: pypy/dist/pypy/doc/draft-dynamic-language-translation.txt
==============================================================================
--- pypy/dist/pypy/doc/draft-dynamic-language-translation.txt	(original)
+++ pypy/dist/pypy/doc/draft-dynamic-language-translation.txt	Mon Sep 12 17:47:04 2005
@@ -65,7 +65,7 @@
 
 The global picture is then to run the program while switching between the flow object space for static enough functions, and a normal, concrete object space for functions or initializations requiring the full dynamism.
 
-If the placeholders are endowed with a bit more information, e.g. if they carry a type information that is propagated to resulting placeholders by individual operations, then our abstract interpretation simultaneously performs type inference.  This is, in essence, executing the program while abstracting out some concrete values and replacing them with the set of all values that could actually be there.  If the sets are broad enough, then after some time we will have seen all potential value sets along each possible code paths, and our program analysis is complete.
+If the placeholders are endowed with a bit more information, e.g. if they carry a type information that is propagated to resulting placeholders by individual operations, then our abstract interpretation simultaneously performs type inference.  This is, in essence, executing the program while abstracting out some concrete values and replacing them with the set of all values that could actually be there.  If the sets are broad enough, then after some time we will have seen all potential value sets along each possible code paths, and our program analysis is complete.  An object space is thus an *interpretation domain*; the Flow Object Space is an *abstract interpretation domain*.
 
 This is a theoretical point of view that differs significantly from what we have implemented, for many reasons.  Of course, the devil is in the details -- which the rest of this paper is all about.
 



More information about the Pypy-commit mailing list