viff

changeset 605:05c7f58fae6e

Fixed broken documentation link.
author Martin Geisler <mg@daimi.au.dk>
date Tue, 25 Mar 2008 15:05:55 +0100
parents 7bf246416d4c
children ab8ab275dbd2
files viff/runtime.py
diffstat 1 files changed, 4 insertions(+), 3 deletions(-) [+]
line diff
     1.1 --- a/viff/runtime.py	Tue Mar 25 14:54:42 2008 +0100
     1.2 +++ b/viff/runtime.py	Tue Mar 25 15:05:55 2008 +0100
     1.3 @@ -251,9 +251,10 @@
     1.4          #: Instead, a I{tree} is made, which follows the tree of
     1.5          #: execution. At the top level the program counter starts at
     1.6          #: C{[0]}. At the next operation it becomes C{[1]}, and so on.
     1.7 -        #: If a callback is scheduled (see L{callback}) at program
     1.8 -        #: counter C{[x, y, z]}, any calls it makes will be numbered
     1.9 -        #: C{[x, y, z, 1]}, then C{[x, y, z, 2]}, and so on.
    1.10 +        #: If a callback is scheduled (see
    1.11 +        #: L{Runtime.schedule_callback}) at program counter C{[x, y,
    1.12 +        #: z]}, any calls it makes will be numbered C{[x, y, z, 1]},
    1.13 +        #: then C{[x, y, z, 2]}, and so on.
    1.14          #:
    1.15          #: Maintaining such a tree of program counters ensures that
    1.16          #: different parts of the program execution never reuses the