viff

changeset 616:c5d4e1fe7c42

Fixed epydoc link errors.
author Martin Geisler <mg@daimi.au.dk>
date Fri, 28 Mar 2008 23:43:16 +0100
parents 743ac108951a
children fd0bd80695b3
files viff/runtime.py
diffstat 1 files changed, 5 insertions(+), 5 deletions(-) [+]
line diff
     1.1 --- a/viff/runtime.py	Fri Mar 28 23:38:07 2008 +0100
     1.2 +++ b/viff/runtime.py	Fri Mar 28 23:43:16 2008 +0100
     1.3 @@ -413,9 +413,9 @@
     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 L{schedule_callback}) at
    1.11 +        #: program counter C{[x, y, z]}, any calls it makes will be
    1.12 +        #: numbered C{[x, y, z, 1]}, then C{[x, y, z, 2]}, and so on.
    1.13          #:
    1.14          #: Maintaining such a tree of program counters ensures that
    1.15          #: different parts of the program execution never reuses the
    1.16 @@ -423,8 +423,8 @@
    1.17          #:
    1.18          #: The L{increment_pc} decorator is responsible for
    1.19          #: dynamically building the tree as the execution unfolds and
    1.20 -        #: L{callback} is responsible for scheduling callbacks with
    1.21 -        #: the correct program counter.
    1.22 +        #: L{schedule_callback} is responsible for scheduling
    1.23 +        #: callbacks with the correct program counter.
    1.24          #:
    1.25          #: @type: C{list} of integers.
    1.26          self.program_counter = [0]