<?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: useful IIf for Visual Basic 2005</title>
	<atom:link href="http://journal.nullschool.net/2005/06/08/useful-iif-for-visual-basic-2005/feed/" rel="self" type="application/rss+xml" />
	<link>http://journal.nullschool.net/2005/06/08/useful-iif-for-visual-basic-2005/</link>
	<description>Cameron Beccario's Journal</description>
	<pubDate>Tue, 06 Jan 2009 10:41:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Cameron Beccario</title>
		<link>http://journal.nullschool.net/2005/06/08/useful-iif-for-visual-basic-2005/#comment-14</link>
		<dc:creator>Cameron Beccario</dc:creator>
		<pubDate>Fri, 17 Jun 2005 06:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://ben.asmallorange.com/~cambecc/journal/2005/06/08/useful-iif-for-visual-basic-2005/#comment-14</guid>
		<description>Actually, through a feature called "type inferencing", you don't need to specify the type parameters of a generic function. The Visual Basic compiler will determine/infer the correct set of type parameters based on the types of the arguments you call the function with. In the example above, it will infer the type Integer because 10 and 20 are Integer literals. Don't worry, if it can't figure it out, the compiler will give you an error. It won't do anything surprising/unintuitive.

See also this &lt;a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/vb2005_generics.asp
"&gt;excellent paper&lt;/a&gt; on VB generics written by my friend and former coworker Harish Kantamneni.</description>
		<content:encoded><![CDATA[<p>Actually, through a feature called &#8220;type inferencing&#8221;, you don&#8217;t need to specify the type parameters of a generic function. The Visual Basic compiler will determine/infer the correct set of type parameters based on the types of the arguments you call the function with. In the example above, it will infer the type Integer because 10 and 20 are Integer literals. Don&#8217;t worry, if it can&#8217;t figure it out, the compiler will give you an error. It won&#8217;t do anything surprising/unintuitive.</p>
<p>See also this <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/vb2005_generics.asp<br />
">excellent paper</a> on VB generics written by my friend and former coworker Harish Kantamneni.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anand</title>
		<link>http://journal.nullschool.net/2005/06/08/useful-iif-for-visual-basic-2005/#comment-13</link>
		<dc:creator>Anand</dc:creator>
		<pubDate>Thu, 16 Jun 2005 12:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://ben.asmallorange.com/~cambecc/journal/2005/06/08/useful-iif-for-visual-basic-2005/#comment-13</guid>
		<description>Dont you have to do something like IIf(Integer)(SomeCondition(), 10, 20), to pick the correct type??</description>
		<content:encoded><![CDATA[<p>Dont you have to do something like IIf(Integer)(SomeCondition(), 10, 20), to pick the correct type??</p>
]]></content:encoded>
	</item>
</channel>
</rss>
