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

[cfbolz at codespeak.net]

Author: cfbolz
Date: Mon Feb 21 13:03:46 2011
New Revision: 80374

Modified:
   pypy/extradoc/talk/stanford-ee380-2011/abstract.txt
Log:
a typo and a precisification


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	Mon Feb 21 13:03:46 2011
@@ -24,11 +24,11 @@
 the translation toolchain separate.  On the one hand, we keep our
 interpreter simple, and we can easily write interpreters for
 other languages.  We have a complete Prolog interpreter and have
-at least played with versions for Smalltalk and Javascript.  On
+at least played with versions for Smalltalk and JavaScript.  On
 the other hand, the fact that our source interpreter does not
 contain any architectural choices makes for unprecedented
 flexibility.  Our toolchain "weaves" into the final executable
-various aspects including the object model, choice of garbage
+various aspects including the object memory layout, choice of garbage
 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