[pypy-svn] r77911 - pypy/extradoc/talk/pepm2011

[pedronis at codespeak.net]

Author: pedronis
Date: Thu Oct 14 12:19:49 2010
New Revision: 77911

Modified:
   pypy/extradoc/talk/pepm2011/escape-tracing.pdf
   pypy/extradoc/talk/pepm2011/paper.tex
Log:
the escaping is not needed

Modified: pypy/extradoc/talk/pepm2011/escape-tracing.pdf
==============================================================================
Binary files. No diff available.

Modified: pypy/extradoc/talk/pepm2011/paper.tex
==============================================================================
--- pypy/extradoc/talk/pepm2011/paper.tex	(original)
+++ pypy/extradoc/talk/pepm2011/paper.tex	Thu Oct 14 12:19:49 2010
@@ -467,9 +467,9 @@
     \item \lstinline{new} corresponds to object creation.
     \item \lstinline{get} correspond to attribute reads.
     \item \lstinline{set} correspond to attribute writes.
-    \item \lstinline{guard\_class} correspond to method calls and are followed by
+    \item \lstinline{guard_class} correspond to method calls and are followed by
     the trace of the called method.
-    \item \lstinline{int\_add} and \lstinline{int\_get} are integer addition and
+    \item \lstinline{int_add} and \lstinline{int_get} are integer addition and
     comparison (``greater than''), respectively.
 \end{itemize}
 
@@ -484,7 +484,7 @@
 using the interpreter.
 
 The trace shows the inefficiencies of \lstinline{f} clearly, if one looks at the
-number of \lstinline{new}, \lstinline{set/get} and \lstinline{guard\_class} operations.
+number of \lstinline{new}, \lstinline{set/get} and \lstinline{guard_class} operations.
 In the rest of the paper we will see how this trace can be optimized using
 partial evaluation.