C that setjmps -> haskell -> C that might longjmp
twhitehead at gmail.com
Tue Mar 2 13:41:17 EST 2010
On March 2, 2010 06:17:46 Simon Marlow wrote:
> For now I suggest you use setjmp. If you want to suggest an API to tell
> the RTS about a longjmp, then perhaps we could implement something, but
> I'm not sure what the API would look like, because you don't have a
> handle to the in-progress calls. In RTS-speak you need to tell the RTS
> about which Tasks have been terminated. I've actually been tinkering
> with this code a bit recently so there is now a structure called InCall
> which replaces some of what Task was for, but the idea is similar.
I haven't quite managed to wrap my head around how the os threads, haskell
threads, tasks, and capabilities all fits together in the rts, so I don't have
any ideas to suggest for a relevant API.
I'll setjmp wrap them. I was guessing that was the most likely option. : )
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.haskell.org/pipermail/glasgow-haskell-users/attachments/20100302/4da4401b/attachment-0001.bin
More information about the Glasgow-haskell-users