… | |
… | |
279 | |
279 | |
280 | 1; |
280 | 1; |
281 | |
281 | |
282 | =head1 BUGS/LIMITATIONS |
282 | =head1 BUGS/LIMITATIONS |
283 | |
283 | |
284 | - could be faster, especially when the core would introduce special |
284 | - you must make very sure that no coro is still active on global destruction. |
285 | support for coroutines (like it does for threads). |
285 | very bad things might happen otherwise (usually segfaults). |
286 | - there is still a memleak on coroutine termination that I could not |
|
|
287 | identify. Could be as small as a single SV. |
|
|
288 | - this module is not well-tested. |
|
|
289 | - if variables or arguments "disappear" (become undef) or become |
|
|
290 | corrupted please contact the author so he cen iron out the |
|
|
291 | remaining bugs. |
|
|
292 | - this module is not thread-safe. You must only ever use this module from |
286 | - this module is not thread-safe. You must only ever use this module from |
293 | the same thread (this requirement might be loosened in the future to |
287 | the same thread (this requirement might be loosened in the future to |
294 | allow per-thread schedulers, but Coro::State does not yet allow this). |
288 | allow per-thread schedulers, but Coro::State does not yet allow this). |
295 | |
289 | |
296 | =head1 SEE ALSO |
290 | =head1 SEE ALSO |