Fix code being interpreted as a target.

This commit is contained in:
Georg Brandl 2007-10-20 13:22:53 +00:00
parent 9b5e23148b
commit ff27e0cd10

View file

@ -523,9 +523,9 @@ Miscellaneous opcodes.
context manager's :meth:`__exit__` bound method. Below that are 1--3 values context manager's :meth:`__exit__` bound method. Below that are 1--3 values
indicating how/why the finally clause was entered: indicating how/why the finally clause was entered:
* SECOND = None * SECOND = ``None``
* (SECOND, THIRD) = (WHY_{RETURN,CONTINUE}), retval * (SECOND, THIRD) = (``WHY_{RETURN,CONTINUE}``), retval
* SECOND = WHY_\*; no retval below it * SECOND = ``WHY_*``; no retval below it
* (SECOND, THIRD, FOURTH) = exc_info() * (SECOND, THIRD, FOURTH) = exc_info()
In the last case, ``TOS(SECOND, THIRD, FOURTH)`` is called, otherwise In the last case, ``TOS(SECOND, THIRD, FOURTH)`` is called, otherwise
@ -535,6 +535,8 @@ Miscellaneous opcodes.
returns a 'true' value, this information is "zapped", to prevent ``END_FINALLY`` returns a 'true' value, this information is "zapped", to prevent ``END_FINALLY``
from re-raising the exception. (But non-local gotos should still be resumed.) from re-raising the exception. (But non-local gotos should still be resumed.)
.. XXX explain the WHY stuff!
All of the following opcodes expect arguments. An argument is two bytes, with All of the following opcodes expect arguments. An argument is two bytes, with
the more significant byte last. the more significant byte last.