<?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>The Shape of Code &#187; heap</title>
	<atom:link href="http://shape-of-code.coding-guidelines.com/tag/heap/feed/" rel="self" type="application/rss+xml" />
	<link>http://shape-of-code.coding-guidelines.com</link>
	<description></description>
	<lastBuildDate>Sun, 29 Jan 2012 23:49:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Naming used to predict object lifetime</title>
		<link>http://shape-of-code.coding-guidelines.com/2008/12/05/naming-used-to-predict-object-lifetime/</link>
		<comments>http://shape-of-code.coding-guidelines.com/2008/12/05/naming-used-to-predict-object-lifetime/#comments</comments>
		<pubDate>Fri, 05 Dec 2008 21:39:44 +0000</pubDate>
		<dc:creator>Derek-Jones</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[heap]]></category>
		<category><![CDATA[lifetime]]></category>
		<category><![CDATA[naming]]></category>

		<guid isPermaLink="false">http://shape-of-code.coding-guidelines.com/?p=20</guid>
		<description><![CDATA[One of the most surprising empirical results I heard about this year was that the name of a Java object could (reasonably) reliably be used to predict its lifetime on the heap. Being a huge advocate of the importance of naming I should not have been surprised. The author , Jeremy Singer, invited me to [...]]]></description>
			<content:encoded><![CDATA[<p>One of the most surprising <a href="http://www.cs.man.ac.uk/~jsinger/pdfs/oopsla_sub.pdf">empirical results I heard about</a> this year was that the name of a Java object could (reasonably) reliably be used to predict its lifetime on the heap.  Being a huge advocate of the <a href="http://www.coding-guidelines.com/cbook/sent792.pdf">importance of naming</a> I should not have been surprised.</p>
<p>The author , <a href="http://www.cs.man.ac.uk/~jsinger/">Jeremy Singer</a>, invited me to Manchester to <a href="http://www.cs.manchester.ac.uk/research/seminars/school/abstracts.html?date=1224630000">talk about my own experiments</a> and I heard about his group&#8217;s latest project investigating how to subdivide a Java program so that bits of it can be executed on different processors.  I suggested various ways in which naming might be used to group semantically related functionality (would it do better than simple statement colocation you ask) and await to see if the group goes with any naming ideas (my suggestions were accompanied by a fair amount of arm waving, so I might have to wait a while).</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fshape-of-code.coding-guidelines.com%2F2008%2F12%2F05%2Fnaming-used-to-predict-object-lifetime%2F&amp;title=Naming%20used%20to%20predict%20object%20lifetime" id="wpa2a_2"><img src="http://shape-of-code.coding-guidelines.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://shape-of-code.coding-guidelines.com/2008/12/05/naming-used-to-predict-object-lifetime/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

