On Fri 15 Mar 2013 22:01, Brent Pinkney b...@4dst.com writes:
When I resume the continuation in another thread, all works perfectly
UNLESS the continued execution throws and exception.
Then guile exits with a core dump.
By contrast if I resume the continuation in the same thread and then
On 03/21/13 11:43, Andy Wingo wrote:
On Fri 15 Mar 2013 22:01, Brent Pinkney b...@4dst.com writes:
When I resume the continuation in another thread, all works perfectly
UNLESS the continued execution throws and exception.
Then guile exits with a core dump.
By contrast if I resume the
On Thu 21 Mar 2013 14:53, Andrew Gaylard a...@computer.org writes:
(catch #t
(λ ()
(throw 'oops)) ; should not crash the vm
(λ ()
(display Success!)(newline))) ; never reached
the VM still cores; Success is never shown. However, you've probably
spotted my mistake: the handler should be (λ
On 03/15/13 23:30, Andy Wingo wrote:
On Fri 15 Mar 2013 22:01, Brent Pinkney b...@4dst.com writes:
I am using partial continuations to resume a computation when an
external system returns with an answer.
I am using (call-with-prompt ...) and (abort-to-prompt)
When I resume the continuation in
Hi,
I am using partial continuations to resume a computation when an
external system returns with an answer.
I am using (call-with-prompt ...) and (abort-to-prompt)
When I resume the continuation in another thread, all works perfectly
UNLESS the continued execution throws and exception.
Hi,
On Fri 15 Mar 2013 22:01, Brent Pinkney b...@4dst.com writes:
I am using partial continuations to resume a computation when an
external system returns with an answer.
I am using (call-with-prompt ...) and (abort-to-prompt)
When I resume the continuation in another thread, all works
