[pypy-svn] r60638 - pypy/extradoc/talk/ecoop2009

antocuni at codespeak.net antocuni at codespeak.net
Sat Dec 20 14:27:19 CET 2008


Author: antocuni
Date: Sat Dec 20 14:27:16 2008
New Revision: 60638

Modified:
   pypy/extradoc/talk/ecoop2009/benchmarks.tex
   pypy/extradoc/talk/ecoop2009/tlc.tex
Log:
comment out a possible confusing example, and add an XXX


Modified: pypy/extradoc/talk/ecoop2009/benchmarks.tex
==============================================================================
--- pypy/extradoc/talk/ecoop2009/benchmarks.tex	(original)
+++ pypy/extradoc/talk/ecoop2009/benchmarks.tex	Sat Dec 20 14:27:16 2008
@@ -40,6 +40,9 @@
 finished the job:
 
 \cfbolz{I think we can kill this for space reasons}
+\anto{If we decide to keep them, we must remember to explain the python-like
+  syntax, as it is no longer in tlc.tex}
+
 \begin{lstlisting}
 def main(n):
     result = 1

Modified: pypy/extradoc/talk/ecoop2009/tlc.tex
==============================================================================
--- pypy/extradoc/talk/ecoop2009/tlc.tex	(original)
+++ pypy/extradoc/talk/ecoop2009/tlc.tex	Sat Dec 20 14:27:16 2008
@@ -77,7 +77,7 @@
 \end{itemize}
 
 
-\subsection{TLC examples}
+\subsection{TLC example}
 
 As we said above, TLC exists only at bytecode level; to ease the development
 of TLC programs, we wrote an assembler that generates TLC bytecode. Figure \ref{fig:tlc-abs}
@@ -108,6 +108,11 @@
 \end{center}
 \end{figure}
 
+\commentout{
+
+\anto{I think this example could cause confusion, because the synatx is TOO
+  similar to (R)Python, hence in the next section it could be unclear which is
+  the leves of the examples}
 
 Since reading TLC programs at bytecode level is hard, in this paper we will
 use an invented Python-like syntax to describe examples, although we need to
@@ -120,3 +125,4 @@
         return -n
     return n
 \end{lstlisting}
+}



More information about the Pypy-commit mailing list