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

arigo at codespeak.net arigo at codespeak.net
Sun Nov 26 22:58:32 CET 2006


Author: arigo
Date: Sun Nov 26 22:58:30 2006
New Revision: 35008

Modified:
   pypy/dist/pypy/doc/stackless.txt
Log:
Typoi.


Modified: pypy/dist/pypy/doc/stackless.txt
==============================================================================
--- pypy/dist/pypy/doc/stackless.txt	(original)
+++ pypy/dist/pypy/doc/stackless.txt	Sun Nov 26 22:58:30 2006
@@ -268,8 +268,9 @@
 are not normally picklable in CPython.  Here again, the `Stackless
 Python`_ implementation has paved the way, and we follow the same
 general design decisions: simple internal objects like bound method
-objects and various kind of iterators are supported; frame objects can
-be fully pickled and unpickled (by serializing the bytecode they are
+objects and various kinds of iterators are supported; frame objects can
+be fully pickled and unpickled
+(by serializing a reference to the bytecode they are
 running in addition to all the local variables).  References to globals
 and modules are pickled by name, similarly to references to functions
 and classes in the traditional CPython ``pickle``.
@@ -504,7 +505,7 @@
 
 Although the concept of coroutines is far from new, they have not been
 generally integrated into mainstream languages, or only in limited form
-(like generators in Python and iterators C#).  We can argue that a
+(like generators in Python and iterators in C#).  We can argue that a
 possible reason for that is that they do not scale well when a program's
 complexity increases: they look attractive in small examples, but the
 models that require explicit switching, by naming the target coroutine,



More information about the Pypy-commit mailing list