<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Static Cling</title>
	<atom:link href="http://www.programmersparadox.com/2008/02/19/static-cling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.programmersparadox.com/2008/02/19/static-cling/</link>
	<description>Is anything I write real?</description>
	<pubDate>Thu, 20 Nov 2008 13:45:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Mark</title>
		<link>http://www.programmersparadox.com/2008/02/19/static-cling/#comment-108</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 21 Feb 2008 03:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2008/02/19/static-cling/#comment-108</guid>
		<description>Tom -

With the likes of Erlang and other functional languages, static state isn't even an issue since it doesn't exist and the programmer therefore doesn't even have to think about constructs such as share memory and semaphores.  

While on a small level it can be easy to manage share state, as applications scale bugs in shared state can become incredibly difficult to deal with it, and I think it is an area many programmers are weak in.

I think there are two options to deal with this: either eliminate shared state, or else do a much better job teaching how to manage shared state than is currently done.  Option one seems like the much easier option to achieve.</description>
		<content:encoded><![CDATA[<p>Tom -</p>
<p>With the likes of Erlang and other functional languages, static state isn&#8217;t even an issue since it doesn&#8217;t exist and the programmer therefore doesn&#8217;t even have to think about constructs such as share memory and semaphores.  </p>
<p>While on a small level it can be easy to manage share state, as applications scale bugs in shared state can become incredibly difficult to deal with it, and I think it is an area many programmers are weak in.</p>
<p>I think there are two options to deal with this: either eliminate shared state, or else do a much better job teaching how to manage shared state than is currently done.  Option one seems like the much easier option to achieve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom R</title>
		<link>http://www.programmersparadox.com/2008/02/19/static-cling/#comment-105</link>
		<dc:creator>Tom R</dc:creator>
		<pubDate>Wed, 20 Feb 2008 04:01:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2008/02/19/static-cling/#comment-105</guid>
		<description>Static Variables have real uses in multi-threaded applications where shared memory is needed to relay information.  Like many things in Computer Science, tools such as static can be abused - but only because the developer who leveraged the technology didn't know what they were doing.

If you develop static/shared memory code with either "write once, ready many" or mutex/semaphores in mind - its fairly safe and easy to manage.</description>
		<content:encoded><![CDATA[<p>Static Variables have real uses in multi-threaded applications where shared memory is needed to relay information.  Like many things in Computer Science, tools such as static can be abused - but only because the developer who leveraged the technology didn&#8217;t know what they were doing.</p>
<p>If you develop static/shared memory code with either &#8220;write once, ready many&#8221; or mutex/semaphores in mind - its fairly safe and easy to manage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Smith</title>
		<link>http://www.programmersparadox.com/2008/02/19/static-cling/#comment-104</link>
		<dc:creator>Kevin Smith</dc:creator>
		<pubDate>Wed, 20 Feb 2008 03:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2008/02/19/static-cling/#comment-104</guid>
		<description>Static state is so bad that I refuse to use it 9 times out of 10. I have scars from dealing with at least 3 of the six reasons listed (concurrency, re-entrancy, memory management for those who care).</description>
		<content:encoded><![CDATA[<p>Static state is so bad that I refuse to use it 9 times out of 10. I have scars from dealing with at least 3 of the six reasons listed (concurrency, re-entrancy, memory management for those who care).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
