[pypy-svn] r80369 - pypy/extradoc/talk/stanford-ee380-2011

[arigo at codespeak.net]

Author: arigo
Date: Sun Feb 20 18:06:05 2011
New Revision: 80369

Modified:
   pypy/extradoc/talk/stanford-ee380-2011/abstract.txt
Log:
Mention Stackless.

Modified: pypy/extradoc/talk/stanford-ee380-2011/abstract.txt
==============================================================================
--- pypy/extradoc/talk/stanford-ee380-2011/abstract.txt	(original)
+++ pypy/extradoc/talk/stanford-ee380-2011/abstract.txt	Sun Feb 20 18:06:05 2011
@@ -29,7 +29,8 @@
 contain any architectural choices makes for unprecedented
 flexibility.  Our toolchain "weaves" into the final executable
 various aspects including the object model, choice of garbage
-collection (GC), choice of backend (C/JVM/.NET), and even the
+collection (GC), of execution model (regular vs. "Stackless"),
+choice of backend (C/JVM/.NET), and even the
 Just-in-Time Compiler (JIT).  There are great practical benefits
 to this.  For example, CPython's GC is stuck with using reference
 counting, while we offer a number of choices.  I will explain how