[pypy-svn] r48293 - pypy/extradoc/talk/roadshow-ibm

pedronis at codespeak.net pedronis at codespeak.net
Sun Nov 4 16:31:43 CET 2007


Author: pedronis
Date: Sun Nov  4 16:31:41 2007
New Revision: 48293

Modified:
   pypy/extradoc/talk/roadshow-ibm/talk.txt
Log:
fix some typos



Modified: pypy/extradoc/talk/roadshow-ibm/talk.txt
==============================================================================
--- pypy/extradoc/talk/roadshow-ibm/talk.txt	(original)
+++ pypy/extradoc/talk/roadshow-ibm/talk.txt	Sun Nov  4 16:31:41 2007
@@ -16,7 +16,7 @@
 
 What PyPy does is setup enough infrastructure such that speed is regained
 and features requiring low-level manipulations are (re-)added as aspects
-without cluttering the intepreter.
+without cluttering the interpreter.
 
 Targets as different as C and the industry OO VMs (JVM, CLR) are supported.
 
@@ -32,7 +32,7 @@
 
 Folk Wisdom about Interpreters for Dynamic Languages
 ====================================================
-* There are unavoidable tradeoffs between flexibilty, maintainability,
+* There are unavoidable tradeoffs between flexibility, maintainability,
   and speed
 
 * Fast, Maintainable, Flexible -- pick one
@@ -40,7 +40,7 @@
 What this means in Practice
 ===========================
 
-Current popular open source dynamic language implemtations:
+Current popular open source dynamic language implementations:
 
 * are relatively slow
 
@@ -59,7 +59,7 @@
 * are harder to maintain than we would like them to be
 
 - because they are traditionally written in low-level languages
-- the language community, which generates experts in the dynamic langauge,
+- the language community, which generates experts in the dynamic language,
   can not use this expertise in its own maintenance.  Instead, expertise
   in C, or C++ is usually needed.
 - every time a new VM is needed, there is a fork in the language community.
@@ -82,7 +82,7 @@
 Translation: Going from interpreters to VMs
 ==============================================
 
-In PyPy interpreteres are written in RPython:
+In PyPy interpreters are written in RPython:
 a subset of Python amenable to static analysis.
 RPython itself still has garbage collection support
 and rich built-in types.



More information about the Pypy-commit mailing list