tag:blogger.com,1999:blog-13073795.post7113548786602642271..comments2023-03-10T08:31:14.101-05:00Comments on Scheming: Quick Note on Continuations to comp.lang.schemeWill Farrhttp://www.blogger.com/profile/11756898910041903896noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-13073795.post-55621845985351724652007-09-10T11:46:00.000-04:002007-09-10T11:46:00.000-04:00A few years back I did some talks on Scheme cont...A few years back I did <A HREF="http://people.csail.mit.edu/jhbrown/scheme/" REL="nofollow"> some talks </A> on Scheme continuations. In <A HREF="http://people.csail.mit.edu/jhbrown/scheme/continuationslides04.pdf" REL="nofollow"> the slides,</A> I tried to describe continuations in terms of closures. In particular, if you think about what is stored so that you can return from a function, it's Jeremyhttps://www.blogger.com/profile/16996359527390032707noreply@blogger.comtag:blogger.com,1999:blog-13073795.post-47287523425281058532007-09-08T20:04:00.000-04:002007-09-08T20:04:00.000-04:00A while ago I tried to explain continuations in a ...A while ago I tried to explain continuations in a similar fashion -- more mechanical than theoretical. It might be helpful to readers here too: <A HREF="http://blog.ianbicking.org/continuations-a-concrete-approach.html" REL="nofollow">http://blog.ianbicking.org/continuations-a-concrete-approach.html</A>Ian Bickinghttps://www.blogger.com/profile/10921115783730718101noreply@blogger.comtag:blogger.com,1999:blog-13073795.post-80575822857630529862007-09-08T15:52:00.000-04:002007-09-08T15:52:00.000-04:00The way I like to think of call/cc, is to picture ...The way I like to think of call/cc, is to picture how it works compared to a normal stack based language. Conceptually, call/cc captures the entire current program stack and creates a "magic function" that, when called, will abort the current stack and restore the original one. The function that you pass to call/cc then gets called with this "magic function" as a parameter.<BR/><BR/>The Unknownhttps://www.blogger.com/profile/08202200535827128776noreply@blogger.com