Author: Maciej Fijalkowski <[email protected]>
Branch:
Changeset: r75772:3b020d7a1cff
Date: 2015-02-08 21:57 +0200
http://bitbucket.org/pypy/pypy/changeset/3b020d7a1cff/
Log: merge
diff --git a/pypy/doc/interpreter-optimizations.rst
b/pypy/doc/interpreter-optimizations.rst
--- a/pypy/doc/interpreter-optimizations.rst
+++ b/pypy/doc/interpreter-optimizations.rst
@@ -165,7 +165,7 @@
We improved this by keeping method lookup separated from method call, unlike
some other approaches, but using the value stack as a cache instead of building
a temporary object. We extended the bytecode compiler to (optionally) generate
-the following code for ``obj.meth(x)``::
+the following code for ``obj.meth(x, y)``::
LOAD_GLOBAL obj
LOOKUP_METHOD meth
@@ -181,7 +181,7 @@
the attribute actually refers to a function object from the class; when this is
not the case, ``LOOKUP_METHOD`` still pushes two values, but one *(im_func)* is
simply the regular result that ``LOAD_ATTR`` would have returned, and the other
-*(im_self)* is a None placeholder.
+*(im_self)* is an interpreter-level None placeholder.
After pushing the arguments, the layout of the stack in the above
example is as follows (the stack grows upwards):
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
