[pypy-svn] r43602 - pypy/extradoc/talk/dyla2007

arigo at codespeak.net arigo at codespeak.net
Thu May 24 18:01:35 CEST 2007


Author: arigo
Date: Thu May 24 18:01:34 2007
New Revision: 43602

Modified:
   pypy/extradoc/talk/dyla2007/outline.txt
Log:
Outline tweaks.


Modified: pypy/extradoc/talk/dyla2007/outline.txt
==============================================================================
--- pypy/extradoc/talk/dyla2007/outline.txt	(original)
+++ pypy/extradoc/talk/dyla2007/outline.txt	Thu May 24 18:01:34 2007
@@ -90,18 +90,18 @@
 - PyPy architecture in metaprogramming terms: 
   * very expressive object language (RPython) for language VMs and semantics 
   * very expressive metalanguage (Python) for analysis and susccessive transformation 
-  * SSI for representing VM spec on meta level 
   * transformations add aspects and specialize to fit 
     virtual or hardware runtime environment 
 
 - Makes interpreters easy to write, update, and generally experiment with
   * more expressiveness helps on all levels (use d12's
-    security references and texts)
+    security references and texts, mention the thunk space)
   * the requirement "specify an interpreter for your language" is much
     less strong than "fit it into the OO VM's model" [e.g. Pyrolog on .NET]
   * transformations [Stackless]
 
 - We can get similarly good GCs and tools
+  * (if we really want - still less work than writing a complete good OO VM)
   * no easier or harder than what needs to be put in an OO VM
   * existing GCs can also be reused
   * a metaprogramming translation toolchain requires a lot of work,



More information about the Pypy-commit mailing list