[pypy-svn] r58061 - pypy/extradoc/talk/osdc2008

[hpk at codespeak.net]

Author: hpk
Date: Thu Sep 11 11:45:55 2008
New Revision: 58061

Modified:
   pypy/extradoc/talk/osdc2008/paper.txt
Log:
some comments in the form of XXX 


Modified: pypy/extradoc/talk/osdc2008/paper.txt
==============================================================================
--- pypy/extradoc/talk/osdc2008/paper.txt	(original)
+++ pypy/extradoc/talk/osdc2008/paper.txt	Thu Sep 11 11:45:55 2008
@@ -3,6 +3,10 @@
 
 :author: Michael Hudson <micahel at gmail.com>
 
+XXX the focus in the paper shifts from translation framework  
+XXX to pypy as python interpreter.  I'd recommend to up-front
+XXX distinguish more clearly.  
+
 Abstract
 --------
 
@@ -48,6 +52,11 @@
 Motivation
 ----------
 
+XXX it's good to highlight the shared idea/value of 
+XXX focusing on implementation rather than language design 
+XXX (it's till the case today, i'd say). 
+XXX if it's meant to tell how PyPy came about it's a mispresentation though
+
 The beginnings PyPy can be traced to the first EuroPython conference
 in 2002, where some of the people who ultimately became involved in
 the project met in person for the first time, and realized they had a
@@ -149,11 +158,16 @@
 Status
 ------
 
+XXX some words about GCs, memory usage? 
+
 PyPy when translated with the C backend (often called pypy-c) and most
 optimizations enabled is currently a reasonably fast and extremely
 conformant implementation of Python 2.4.4.
 XXX is conformant a word?
 
+XXX isn't it a wider range like 0.8 to 5 times, see e.g. recent sympy feedback on pypy-dev from Ondrej
+with an emphasis on it rather being slower usually? 
+
 Reasonably fast: depending on the code being run, pypy-c ranges from
 being 20% faster to about twice as slow as CPython (the
 still-experimental Just-In-Time compiler runs some (admittedly
@@ -176,6 +190,8 @@
 
 The former is usually a much more significant problem, of course.
 
+XXX mention sandboxing as a distinguished feature?  
+
 Compatibility with Python 2.5 is almost complete in a branch.  2.6
 shouldn't be too hard.  No Python 3 yet :)
 
@@ -190,6 +206,7 @@
 
 PyPy started as a classic open-source, spare-time project, was funded
 for a while, and is currently mostly a spare-time project again.
+XXX not a completely adequate description, e.g. google contracts
 
 Right from the start, however, the project was driven along by
 *sprints* -- focused week long coding sessions.  During the funding
@@ -206,6 +223,11 @@
 already extended the state of the art in automatically generating a
 JIT compiler for an implementation of a dynamic language.
 
+XXX mention that PyPy provides unprecedented possibilities in 
+    producing Interpreters for specific environments (memory-constrained, 
+    sandboxing, gaming-engines etc.) ?  (hpk) i at least think it's a 
+    very exciting area as well. 
+
 Down at the more nuts and bolts implementation level, something I'm
 interested in myself is stealing ideas -- and maybe even code -- from
 garbage collectors developed by the Jikes RVM project.