… | |
… | |
356 | |
356 | |
357 | It probably only works on perl 5.10; it cannot clone a coroutine inside |
357 | It probably only works on perl 5.10; it cannot clone a coroutine inside |
358 | the substition operator (but windows perl can't fork from there either) |
358 | the substition operator (but windows perl can't fork from there either) |
359 | and some other contexts, and C<abort ()> is the preferred mechanism to |
359 | and some other contexts, and C<abort ()> is the preferred mechanism to |
360 | signal errors. It cannot clone a state that has a c context attached |
360 | signal errors. It cannot clone a state that has a c context attached |
361 | (implementing clone on the C level is too hard for me to even try), which |
361 | (implementing clone on the C level is too hard for me to even try), |
362 | rules out calling call/cc from the main coroutine. It doesn't work with |
362 | which rules out calling call/cc from the main coroutine. It cannot |
|
|
363 | clone a context that hasn't even been started yet. It doesn't work with |
363 | C<-DDEBUGGING> (but what does). It probably also leaks, and sometimes |
364 | C<-DDEBUGGING> (but what does). It probably also leaks, and sometimes |
364 | triggers a few assertions inside Coro. Most of these limitations *are* |
365 | triggers a few assertions inside Coro. Most of these limitations *are* |
365 | fixable with some effort, but that's pointless just to make a point that |
366 | fixable with some effort, but that's pointless just to make a point that |
366 | it could be done. |
367 | it could be done. |
367 | |
368 | |