[pypy-svn] r53616 - pypy/extradoc/talk/rupy2008

arigo at codespeak.net arigo at codespeak.net
Wed Apr 9 16:26:45 CEST 2008


Author: arigo
Date: Wed Apr  9 16:26:44 2008
New Revision: 53616

Modified:
   pypy/extradoc/talk/rupy2008/talk.tex
Log:
Typos.  Minor clarification.


Modified: pypy/extradoc/talk/rupy2008/talk.tex
==============================================================================
--- pypy/extradoc/talk/rupy2008/talk.tex	(original)
+++ pypy/extradoc/talk/rupy2008/talk.tex	Wed Apr  9 16:26:44 2008
@@ -167,7 +167,7 @@
   \item accessing .NET libraries seamlessly from PyPy
   \item ... demo
   \end{itemize}
-\end
+\end{frame}
 
 
 \begin{frame}
@@ -197,7 +197,7 @@
   \begin{itemize}
   \item writing good JITs for dynamic languages is hard work
   \item keeping up with new language features is hard
-  \item compilers are a bad encoding for languag semantics
+  \item compilers are a bad encoding for language semantics
   \pause
   \begin{block}{
     Existing hand-written JITs}
@@ -225,7 +225,7 @@
     \item old idea from CS research
     \item transforms an interpreter into a static compiler
     \item never worked well for real-life examples
-    \item key insight: generating a JIT is \emph{easier}
+    \item key insight: generating a JIT is \emph{easier} than a static compiler
     \end{itemize}
   \end{block}
  
@@ -248,7 +248,7 @@
   \begin{itemize}
   \item we had a working prototype at the end of the EU project
   \item speeds up simple arithmetic functions \emph{a lot}
-  \item had limitations that were hard to fix with
+  \item had limitations that were hard to fix
   \pause
   \item refactoring happened in the last two months to improve the situation
   \item still in progress, but already allows experimentation



More information about the Pypy-commit mailing list