<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Developer On Line - Latest Comments in Stack Wars</title><link>http://dol.disqus.com/</link><description></description><atom:link href="https://dol.disqus.com/stack_wars/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 18 Apr 2009 17:19:54 -0000</lastBuildDate><item><title>Re: Stack Wars</title><link>http://developeronline.blogspot.com/2008/05/stack-wars.html#comment-8337177</link><description>&lt;p&gt;This is also a prime example of tail recursion. A good compiler should be able to spot this and produce the same output for those two functions. The reasoning being that at the second recursive call to step_up() there is really no meaningful state to save on the stack, so rather than actually performing the recursive call we can just reuse the current stack frame by jumping back up to the top of the currently executing function (which is exactly what you're doing in the second solution).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Johannes</dc:creator><pubDate>Sat, 18 Apr 2009 17:19:54 -0000</pubDate></item><item><title>Re: Stack Wars</title><link>http://developeronline.blogspot.com/2008/05/stack-wars.html#comment-549213</link><description>&lt;p&gt;very nice article panefsky!&lt;br&gt;keep on&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">marta</dc:creator><pubDate>Thu, 29 May 2008 10:21:39 -0000</pubDate></item><item><title>Re: Stack Wars</title><link>http://developeronline.blogspot.com/2008/05/stack-wars.html#comment-519700</link><description>&lt;p&gt;Very clean very powerful the way to comput stack usage.&lt;br&gt;It can be useful sometimes&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mohito</dc:creator><pubDate>Fri, 23 May 2008 15:17:57 -0000</pubDate></item></channel></rss>