<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Overheard in the tech blogosphere &#187; buffers</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/overheard/tag/buffers/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/overheard</link>
	<description>A Whatis.com blog</description>
	<lastBuildDate>Tue, 04 Jun 2013 13:36:12 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Understanding the stack and the role of a stack pointer</title>
		<link>http://itknowledgeexchange.techtarget.com/overheard/understanding-the-stack-and-the-role-of-a-stack-pointer/</link>
		<comments>http://itknowledgeexchange.techtarget.com/overheard/understanding-the-stack-and-the-role-of-a-stack-pointer/#comments</comments>
		<pubDate>Mon, 04 Jun 2012 14:02:00 +0000</pubDate>
		<dc:creator>Margaret Rouse</dc:creator>
				<category><![CDATA[buffers]]></category>
		<category><![CDATA[stacks]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/overheard/?p=4071</guid>
		<description><![CDATA[&#8220;By convention, stacks usually grow down. This means that the stack starts at a high address in memory and progressively gets lower.&#8221; &#8212; Ian Wienand Today&#8217;s WhatIs.com Word of the Day is stack pointer, a small register that stores the address of the program request most recently entered into a stack. I have to take [...]]]></description>
				<content:encoded><![CDATA[<table border="0" cellspacing="5" cellpadding="5">
<tbody>
<tr>
<td><a href="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/8/files/2012/06/ian_wienand.jpg"><img class="alignnone size-medium wp-image-4072" src="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/8/files/2012/06/ian_wienand.jpg" alt="" /></a></td>
<td><em>&#8220;By convention, stacks usually grow down. This means that the stack  starts at a high address in memory and progressively gets lower.&#8221;</em> &#8212; <a href="http://www.bottomupcs.com/elements_of_a_process.html">Ian  Wienand</a><br />
<a href="http://www.shopgbmp.org/netovastmadv.html"></a></td>
</tr>
</tbody>
</table>
<p>Today&#8217;s WhatIs.com Word of the Day is <a href="http://whatis.techtarget.com/definition/stack-pointer">stack pointer</a>, a small register that stores the address of the program request most recently entered into a <a href="http://searchcio-midmarket.techtarget.com/definition/stack">stack</a>.</p>
<p>I have to take a minute here to plug Ian Wienand&#8217;s free online book &#8220;Computer Science from the Bottom Up.&#8221;  If you&#8217;re interested in looking underneath the hood, this is the book to help you understand what you&#8217;re seeing.</p>
<p>Mr. Wienand explains the concept of a stack as clearly as anyone I&#8217;ve ever heard or read:</p>
<blockquote><p>A stack is generic data structure that works exactly like a stack of plates; you can push an item (put a plate on top of a stack of plates), which then becomes the top item, or you can pop an item (take a plate off, exposing the previous plate).</p>
<p>Stacks are fundamental to function calls. Each time a function is called it gets a new stack frame. This is an area of memory which usually contains, at a minimum, the address to return to when complete, the input arguments to the function and space for local variables.</p></blockquote>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/overheard/understanding-the-stack-and-the-role-of-a-stack-pointer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
