<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Recap! What&#8217;s the stack pointer?</title>
	<link>http://some-antics.com/blog/2007/03/12/recap-whats-the-stack-pointer/</link>
	<description>when i say "some", you think "not all"</description>
	<pubDate>Tue, 06 Jan 2009 09:14:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Aidan Kehoe</title>
		<link>http://some-antics.com/blog/2007/03/12/recap-whats-the-stack-pointer/#comment-2032</link>
		<author>Aidan Kehoe</author>
		<pubDate>Tue, 13 Mar 2007 14:48:17 +0000</pubDate>
		<guid>http://some-antics.com/blog/2007/03/12/recap-whats-the-stack-pointer/#comment-2032</guid>
		<description>What language are you using them with? I didn't understand how to use them in Scheme (and other languages with call/cc) until a few minutes ago, but &lt;a href="http://pyds.muensterland.org/wiki/continuationbasedserver.html" rel="nofollow"&gt;this guy&lt;/a&gt; explains it well: &lt;blockquote&gt;&lt;i&gt;You usually have some function named call/cc (in Scheme) or callcc or whatever. This function just calls another function and passes on the current continuation - the point in control flow that will be executed on return from the call/cc call. The called function now can store this continuation somewhere and [any part of the program can] later [resume that continuation; just invoking it as a function, in Scheme]  to transfer back to the original function.&lt;/i&gt;&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>What language are you using them with? I didn&#8217;t understand how to use them in Scheme (and other languages with call/cc) until a few minutes ago, but <a href="http://pyds.muensterland.org/wiki/continuationbasedserver.html" rel="nofollow">this guy</a> explains it well:<br />
<blockquote><i>You usually have some function named call/cc (in Scheme) or callcc or whatever. This function just calls another function and passes on the current continuation - the point in control flow that will be executed on return from the call/cc call. The called function now can store this continuation somewhere and [any part of the program can] later [resume that continuation; just invoking it as a function, in Scheme]  to transfer back to the original function.</i></p></blockquote>
]]></content:encoded>
	</item>
</channel>
</rss>
