[pypy-svn] r78602 - pypy/extradoc/talk/pycon2011

[cfbolz at codespeak.net]

Author: cfbolz
Date: Sun Oct 31 14:23:27 2010
New Revision: 78602

Modified:
   pypy/extradoc/talk/pycon2011/pypy-optimizations.txt
Log:
small fixes, an XXX


Modified: pypy/extradoc/talk/pycon2011/pypy-optimizations.txt
==============================================================================
--- pypy/extradoc/talk/pycon2011/pypy-optimizations.txt	(original)
+++ pypy/extradoc/talk/pycon2011/pypy-optimizations.txt	Sun Oct 31 14:23:27 2010
@@ -10,14 +10,14 @@
 Classification: Discuss in depth
 Abstract:
 
-The talk would contain a list of features that are hard to optimize in Python,
+The talk will contain a list of features that are hard to optimize in Python,
 why and how we're fixing it in PyPy. This also might be used as a rough guide
 what features in Python are optimizable right now and what are not.
 
 The list of mentioned features is not exhaustive, however we will try to
 focus at least on the following:
 
-* Dynamic language - In Python code we have no known types, like a static
+* Dynamic language - In Python code we have no known types, like a statically typed
   language.  Even operations like "a + b" can do anything, unless we know more
   about the code.
 
@@ -27,10 +27,10 @@
 
 * Object model - All user defined Python objects have a dictionary which stores
   their attributes, as does every type.  When Python does an attribute lookup
-  this requires 2 dictionary lookups.
+  this requires at least two dictionary lookups.
 
-  In PyPy we use an approach similar to one used by v8 with hidden classes
-  (except more pypy specific) called shared dictionaries.
+  In PyPy we use an approach similar to the one used by V8 with hidden classes
+  (except more PyPy specific) called map dictionaries. XXX type versions?
 
 * FFI calls - calling C from Python is costly and hard to optimize. In PyPy we
   decided to go via ctypes, this part will explain how are we going to handle