Andy Wingo 46d2d6f80e allocate variables that are set! on the heap ... * module/system/il/ghil.scm (ghil-lookup): So, it turns out this function needed to be split into three: (ghil-var-is-bound?, ghil-var-for-ref!, ghil-var-for-set!): The different facets of ghil-lookup. Amply commented in the source. The difference being that we now allocate variables that are set! on the heap, so that other continuations see their possibly-modified values. (force-heap-allocation!): New helper. * testsuite/Makefile.am: * testsuite/t-call-cc.scm: New test, that variables that are set! are allocated on the heap, so that subsequent modifications are still seen by the continuation. The test was distilled from test 7.3 in r5rs_pitfall.test.		2008-09-28 23:09:11 +02:00
..
elisp	use #:keywords in module/*.scm, not :keywords	2008-09-09 06:58:25 +02:00
ghil	use #:keywords in module/*.scm, not :keywords	2008-09-09 06:58:25 +02:00
r5rs	use #:keywords in module/*.scm, not :keywords	2008-09-09 06:58:25 +02:00
scheme	allocate variables that are set! on the heap	2008-09-28 23:09:11 +02:00
.cvsignore	*** empty log message ***	2001-04-22 02:13:48 +00:00
Makefile.am	fix Makefile.am in module/language	2008-09-02 10:30:39 -07:00