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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB+yqhr9IW4v3mHtQRAm+UAJ407CXoHF7mU6v2hrIrhZj2otEzigCaAgcx
T5Cq11uu8UHkHbk2rbx+6Wg=
=Knjc
-----END PGP SIGNATURE-----