Download Firefox: WindowsMac OS X
logo       
Google Custom Search
    AddThis Social Bookmark Button

Re: toplevel continuation bug?: msg#00015

Subject: Re: toplevel continuation bug?
On Fri, Jan 28, 2005 at 08:15:56AM -0800, Theodore Bondo wrote:
> Running 1.9.6,
> 
> Say I have the following code in a file:
> 
> (define c 'undefined)
>  
> (call-with-current-continuation
>  (lambda (cc) (set! c cc)))
> 
> and I load that code using (load filename).  Okay,
> everything is fine until I try calling the
> continuation (c 1)- SISC just exits hard.  It exits so
> hard that I have been unable to figure out how to get
> a stack trace.  It seems that I can call the
> continuation while in the file but once the file is
> fully loaded- calling the continuation just exits
> hard.

The problem is that the continuation of an expression executed in the 
REPL is usually the Loop portion of R.E.P.L.  But when loading a file, 
there is no continuation, so when you invoke the continuation captured 
during load, SISC naturally exits, having nothing left to do.  

This is similar to the behavior described in the Note in the Basic 
Thread Operations section of the manual:

http://sisc.sourceforge.net/manual/html/ch06.html#id2569396

        Scott

Attachment: pgpLIsUKVsqbb.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>