| Newsgroups |
gmane.comp.lang.io |
| Message-ID |
<[email protected]> |
The solution I posted earlier should work fine for you :) as long as you resume by sending an io message and not calling IoCoroutine_resume as a c func directly :). And debugging shouldn't be a problem because there is no debugger yet. ;)
But to me this is not a simple bug that should be taken care of with a hotfix, but rather something conceptually that requires design decisions by somebody with more experience. :)
Cheers Jan
----- Reply message -----
From: "petri rokka" <[email protected]>
To: <[email protected]>
Subject: [Io] Coroutines are bastards....
Date: Thu, Jun 9, 2011 15:29
In my application I need to debug/pause/resume an actor which happens to
have exception handling :D.
I really would like this to work!
2011/6/7 Jan-Paul Bultmann <[email protected]>
>
>
> I mean I love the concept, but it is full of quirks and hiccups and could
> really need a ton of polish.^^
> Resuming the right one is difficult, they are hard to handle, and should
> not be referenced, because at any moment a coroutine could pop of a child
> and say goodbye without you noticing. Aaaand when debugging is activated on
> a Coroutine, it doesn't propagate. :/
> So you are debugging an actor? Say goodbye once the actual method call
> occurs leaving the main _actorProcessQueue_ and say hello, once it returns
> there.
> You are debugging a method containing exception handling? Too bad you can't
> look into the exception throwing code because it happened in another
> coroutine. <- that one is actually Io kicking in your face, stealing your
> girlfriend and then laughing mad at you. :D
>
> cheerio Jan
>
>