<?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>Yet Another [À Compléter] &#187; .NET4</title>
	<atom:link href="http://blog.neteril.org/tag/net4/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.neteril.org</link>
	<description>Random thoughts of Jérémie Laval</description>
	<lastBuildDate>Wed, 24 Aug 2011 17:43:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>C#4, .NET 4 and concurrency</title>
		<link>http://blog.neteril.org/2008/10/11/c4-net-4-and-concurrency/</link>
		<comments>http://blog.neteril.org/2008/10/11/c4-net-4-and-concurrency/#comments</comments>
		<pubDate>Sat, 11 Oct 2008 14:48:57 +0000</pubDate>
		<dc:creator>Jérémie Laval</dc:creator>
				<category><![CDATA[C#]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Mono]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[.NET4]]></category>
		<category><![CDATA[C#4]]></category>
		<category><![CDATA[parallelfx]]></category>

		<guid isPermaLink="false">http://garuma.wordpress.com/?p=306</guid>
		<description><![CDATA[<p>ParallelFx has been around for quite a long time now (first CTP was released on December, 2007). Up until now it was a separate library, labeled as an extension and thus bundled in its own assembly. However, today, ParallelFx developers <a href="http://blogs.msdn.com/pfxteam/archive/2008/10/10/8994927.aspx">announced on their blog</a> that the final ParallelFx version should be available as an official part of the upcoming .NET 4 framework.</p>
<p>In addition, with the <acronym title="Professional Developer Conference">PDC</acronym> near the corner, informations are beginning to filtrate about C#4. As can be seen on several videos on <a href="http://channel9.msdn.com/">Channel 9</a> (<a href="http://channel9.msdn.com/posts/Charles/Anders-Hejlsberg-and-Guy-Steele-Concurrency-and-Language-Design/">this one particularly</a>), the C#4 design team is seriously planning to add language features that will help programmers do multi-threaded and concurrent programs.</p>
<p>Most noticeably, Anders speaks, around 5:30, about compiler-enforced purity (which can be already found in other imperative language like <a href="http://www.digitalmars.com/d/2.0/function.html#pure-functions">D</a>) and automatic isolation of objects (I suspect it's a sort of <acronym title="Software Transactional Memory">STM</acronym> where object manipulations are bundled in separate transaction). </p>

<p>Both of them also make very good points about the difficulty for compilers to assert that a piece of code is parallelizable. Since even experienced programmers <a href="http://www.ddj.com/cpp/210600279">can make mistakes</a> about the thread-safety of their code, it appears hard for compiler to automagically assure that a piece of code is indeed side effect free in a imperative world like C# (a problem that language like Haskell don’t know, being pure by default). I also like the position of Anders about C# as an hybrid imperative/functional language.</p>
<p>/me is looking forward to PDC for more parallel goodness and to start implementing these features in Mono <img src="http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif" alt=";-)" class="wp-smiley"> .</p>]]></description>
			<content:encoded><![CDATA[<p>ParallelFx has been around for quite a long time now (first CTP was released on December, 2007). Up until now it was a separate library, labeled as an extension and thus bundled in its own assembly. However, today, ParallelFx developers <a href="http://blogs.msdn.com/pfxteam/archive/2008/10/10/8994927.aspx">announced on their blog</a> that the final ParallelFx version should be available as an official part of the upcoming .NET 4 framework.</p>
<p>In addition, with the <acronym title="Professional Developer Conference">PDC</acronym> near the corner, informations are beginning to filtrate about C#4. As can be seen on several videos on <a href="http://channel9.msdn.com/">Channel 9</a> (<a href="http://channel9.msdn.com/posts/Charles/Anders-Hejlsberg-and-Guy-Steele-Concurrency-and-Language-Design/">this one particularly</a>), the C#4 design team is seriously planning to add language features that will help programmers do multi-threaded and concurrent programs.</p>
<p>Most noticeably, Anders speaks, around 5:30, about compiler-enforced purity (which can be already found in other imperative language like <a href="http://www.digitalmars.com/d/2.0/function.html#pure-functions">D</a>) and automatic isolation of objects (I suspect it&#8217;s a sort of <acronym title="Software Transactional Memory">STM</acronym> where object manipulations are bundled in separate transaction).</p>
<p>Both of them also make very good points about the difficulty for compilers to assert that a piece of code is parallelizable. Since even experienced programmers <a href="http://www.ddj.com/cpp/210600279">can make mistakes</a> about the thread-safety of their code, it appears hard for compiler to automagically assure that a piece of code is indeed side effect free in a imperative world like C# (a problem that language like Haskell don&#8217;t know, being pure by default). I also like the position of Anders about C# as an hybrid imperative/functional language.</p>
<p>/me is looking forward to PDC for more parallel goodness and to start implementing these features in Mono <img src='http://blog.neteril.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  .</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.neteril.org/2008/10/11/c4-net-4-and-concurrency/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

