<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Optional Parameters in C#4, C#3 and VB.Net, With a Side Order of IL Quirks</title>
	<atom:link href="http://www.grumpydev.com/2010/04/19/optional-parameters-in-c4-c3-and-vb-net-with-a-side-order-of-il-quirks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.grumpydev.com/2010/04/19/optional-parameters-in-c4-c3-and-vb-net-with-a-side-order-of-il-quirks/</link>
	<description>The Technical Jibber Jabber of Steven Robbins</description>
	<lastBuildDate>Tue, 13 Dec 2011 14:22:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: bigbyte</title>
		<link>http://www.grumpydev.com/2010/04/19/optional-parameters-in-c4-c3-and-vb-net-with-a-side-order-of-il-quirks/comment-page-1/#comment-265</link>
		<dc:creator>bigbyte</dc:creator>
		<pubDate>Fri, 07 May 2010 22:00:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.grumpydev.com/?p=338#comment-265</guid>
		<description>About the gotchas...
One of your concerns is that since default values are baked into the caller, changing the default value later still creates calls with out-of-date default values. This is primarily if you are creating public APIs for use by anyone on the planet. But that can be easily solved by signing your assemblies. Caller won&#039;t run without matching signature forcing your clients to recompile. If it&#039;s for internal use, people will be recompiling all the time so it is not really a concern.</description>
		<content:encoded><![CDATA[<p>About the gotchas&#8230;<br />
One of your concerns is that since default values are baked into the caller, changing the default value later still creates calls with out-of-date default values. This is primarily if you are creating public APIs for use by anyone on the planet. But that can be easily solved by signing your assemblies. Caller won&#8217;t run without matching signature forcing your clients to recompile. If it&#8217;s for internal use, people will be recompiling all the time so it is not really a concern.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Morning Brew - Chris Alcock &#187; The Morning Brew #583</title>
		<link>http://www.grumpydev.com/2010/04/19/optional-parameters-in-c4-c3-and-vb-net-with-a-side-order-of-il-quirks/comment-page-1/#comment-251</link>
		<dc:creator>The Morning Brew - Chris Alcock &#187; The Morning Brew #583</dc:creator>
		<pubDate>Tue, 20 Apr 2010 07:36:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.grumpydev.com/?p=338#comment-251</guid>
		<description>[...] Optional Parameters in C#4, C#3 and VB.Net, With a Side Order of IL Quirks - Steven Robbins digs into the IL behind Optional and Named parameters looking at this new functionality of C# and exploring how it works behind the scenes [...]</description>
		<content:encoded><![CDATA[<p>[...] Optional Parameters in C#4, C#3 and VB.Net, With a Side Order of IL Quirks &#8211; Steven Robbins digs into the IL behind Optional and Named parameters looking at this new functionality of C# and exploring how it works behind the scenes [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

