<?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: Beware of Java string memory allocation</title>
	<atom:link href="http://www.blueskyonmars.com/2005/04/27/beware-of-java-string-memory-allocation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blueskyonmars.com/2005/04/27/beware-of-java-string-memory-allocation/</link>
	<description>Kevin Dangoor on Software Development</description>
	<pubDate>Mon, 01 Dec 2008 20:18:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Tom Hawtin</title>
		<link>http://www.blueskyonmars.com/2005/04/27/beware-of-java-string-memory-allocation/#comment-712</link>
		<dc:creator>Tom Hawtin</dc:creator>
		<pubDate>Tue, 31 May 2005 20:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/wordpress/?p=1349#comment-712</guid>
		<description>1.5 always copies the backing char[].

With the new Java Memory Model (JMM) in 1.5, all threads are guaranteed to see the correct characters even without any use of synchronisation or volatiles.</description>
		<content:encoded><![CDATA[<p>1.5 always copies the backing char[].</p>
<p>With the new Java Memory Model (JMM) in 1.5, all threads are guaranteed to see the correct characters even without any use of synchronisation or volatiles.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.285 seconds -->
