ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/Coro/Coro/State.pm
(Generate patch)

Comparing Coro/Coro/State.pm (file contents):
Revision 1.91 by root, Sun Mar 2 16:11:12 2008 UTC vs.
Revision 1.92 by root, Sat Apr 5 22:38:27 2008 UTC

… …
267possible. Any Coro::State that starts to use a stack after this call is 267possible. Any Coro::State that starts to use a stack after this call is
268guaranteed this minimum stack size. Please note that Coroutines will 268guaranteed this minimum stack size. Please note that Coroutines will
269only need to use a C-level stack if the interpreter recurses or calls a 269only need to use a C-level stack if the interpreter recurses or calls a
270function in a module that calls back into the interpreter. 270function in a module that calls back into the interpreter.
271 271
272=item Coro::State::force_cctx
273
274Forces the allocation of a C context for the currently running coroutine
275(if not already done). Apart from benchmarking there is little point
276in doing so, however.
277
272=item @states = Coro::State::list 278=item @states = Coro::State::list
273 279
274Returns a list of all states currently allocated. 280Returns a list of all states currently allocated.
275 281
276=cut 282=cut

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines