Error processing request

Parameters

Body

Error

Unknow state transition: LINE -> END

-code

1

-level

0

-errorstack

INNER {returnImm {Unknow state transition: LINE -> END} {}} CALL {my render_wikit yield {Consequence of [NRE], see [coroutine].





----
[DKF]: If you're trying to build a coroutine that yields many values, it can be a little bit tricky to work out how to string the value passing through '''yield''' nicely; the values just don't seem to pass around in a way that feels natural (well, to me anyway). Here's a helper procedure that makes it all much easier:
** Example:  Basic **
proc onetwo {} {
    set val [info coroutine]
    upvar 1 $var v
    while 1 {
        set v [yield $val]
        set val [uplevel 1 $body]
    }
}
======

With this, you get an automatic yield of the name of the coroutine to start with, and then you can pass values in and have results passed back. The given ''var''iable is set to the value passed in, and the result of evaluating the ''body'' is the next value yielded. You might use it like this:

======
proc summerBody n {
proc summerBody {n} {
        incr n $x
    }
}
coroutine s summerBody 0;   # ==> ::s
s 10;                       # ==> 10
s 5;                        # ==> 15
s 2;                        # ==> 17
s 1;                        # ==> 18
======

Without `coloop`, you'd need to write something like this:

======
proc summerBody {n} {
    set x [yield [info coroutine]]
    while 1 {
        set x [yield [incr n $x]]
    }
}
======

Which is not much longer, but ''is'' much less clear as to what value is flowing where. With longer bodies, it becomes even less clear.


----
**See Also**
   * [tcl::unsupported]::[yieldm]
} regexp2} CALL {my render yield {Consequence of [NRE], see [coroutine].





----
[DKF]: If you're trying to build a coroutine that yields many values, it can be a little bit tricky to work out how to string the value passing through '''yield''' nicely; the values just don't seem to pass around in a way that feels natural (well, to me anyway). Here's a helper procedure that makes it all much easier:
** Example:  Basic **
proc onetwo {} {
    set val [info coroutine]
    upvar 1 $var v
    while 1 {
        set v [yield $val]
        set val [uplevel 1 $body]
    }
}
======

With this, you get an automatic yield of the name of the coroutine to start with, and then you can pass values in and have results passed back. The given ''var''iable is set to the value passed in, and the result of evaluating the ''body'' is the next value yielded. You might use it like this:

======
proc summerBody n {
proc summerBody {n} {
        incr n $x
    }
}
coroutine s summerBody 0;   # ==> ::s
s 10;                       # ==> 10
s 5;                        # ==> 15
s 2;                        # ==> 17
s 1;                        # ==> 18
======

Without `coloop`, you'd need to write something like this:

======
proc summerBody {n} {
    set x [yield [info coroutine]]
    while 1 {
        set x [yield [incr n $x]]
    }
}
======

Which is not much longer, but ''is'' much less clear as to what value is flowing where. With longer bodies, it becomes even less clear.


----
**See Also**
   * [tcl::unsupported]::[yieldm]
}} CALL {my revision yield} CALL {::oo::Obj3589039 process revision/yield} CALL {::oo::Obj3589037 process}

-errorcode

NONE

-errorinfo

Unknow state transition: LINE -> END
    while executing
"error $msg"
    (class "::Wiki" method "render_wikit" line 6)
    invoked from within
"my render_$default_markup $N $C $mkup_rendering_engine"
    (class "::Wiki" method "render" line 8)
    invoked from within
"my render $name $C"
    (class "::Wiki" method "revision" line 31)
    invoked from within
"my revision $page"
    (class "::Wiki" method "process" line 56)
    invoked from within
"$server process [string trim $uri /]"

-errorline

4