[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pypy-svn
Subject:    [pypy-svn] r78628 - pypy/extradoc/talk/pycon2011
From:       dan () codespeak ! net
Date:       2010-10-31 23:05:24
Message-ID: 20101031230524.094F1282B90 () codespeak ! net
[Download RAW message or body]

Author: dan
Date: Mon Nov  1 00:05:22 2010
New Revision: 78628

Modified:
   pypy/extradoc/talk/pycon2011/pypy-optimizations.txt
Log:
Reworded a couple sentences and fixed a typo.

Modified: pypy/extradoc/talk/pycon2011/pypy-optimizations.txt
==============================================================================
--- pypy/extradoc/talk/pycon2011/pypy-optimizations.txt	(original)
+++ pypy/extradoc/talk/pycon2011/pypy-optimizations.txt	Mon Nov  1 00:05:22 2010
@@ -7,30 +7,30 @@
 how PyPy is organized, and what optimizations our JIT can do
 (and what it can't do) for your code.
 
-This talk will also contain a brief part about status of the PyPy project,
+This talk will also contain a brief section discussing status of the PyPy project,
 it's goals and achievements.
 
 Session type: Talk
 Classification: Discuss in depth
 Abstract:
 
-The talk will explain a bit in details how a python interpreter works
-internally and why some operations are costly. We'll go through several python
-features, how they work, why they're slow in CPython and how we're fixing it.
+The talk will detail how a python interpreter works internally and why
+some operations are costly. We'll go through several python features,
+how they work, why they're slow in CPython and how we're fixing it.
 
 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 statically
   typed language.  Even operations like "a + b" can do anything, unless we know
-  more about the code, especially associated types.
+  more about the code, and the types it is operating on.
 
 * Frame introspection - Frame objects need to be allocated for every function
   call, and all local variables are stored on the frame, and must be accessible
   from further down the call stack.
 
   PyPy uses a novel approach called "virtualizables" which makes it possible
-  to not allocate frames at all in most common cases.
+  to avoid frame allocation in most common cases.
 
 * Object model - All user defined Python objects have a dictionary which stores
   their attributes, as does every type.  When Python does an attribute lookup
@@ -39,11 +39,11 @@
   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
-  expse C APIs to Python code via ctypes, this part will explain how are we
-  going to handle ctypes calls to be fast.
+* FFI calls - Calling C from Python is costly and hard to optimize. In PyPy we
+  expose C APIs to Python code via ctypes. This part explains how we can 
+  optimize ctypes calls.
 
-* `array` module - users of CPython's array module probably know it can save
+* `array` module - Users of CPython's array module probably know it can save
   them quite a bit of memory, however it's also slower than using a list, due
   to the overhead of boxing and unboxing on every operations. Here we will tie
   everything together and describe how the ``array`` module is much faster with
_______________________________________________
pypy-svn mailing list
pypy-svn@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-svn
[prev in list] [next in list] [prev in thread] [next in thread]