http://blogs.msdn.com/michkap/archive/2007/05/25/2875426.aspxI read Paul Vick's post IIF becomes If, and a true ternary operator and saw that a version of Visual Basic was finally going to have an IIF() that was going to properly short-circuit and not run both conditions. And I thought about how they cheated onen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/michkap/archive/2007/05/25/2875426.aspx#2878457Fri, 25 May 2007 22:01:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:2878457Dennis E. Hamilton<p>Wow, Paul Vick's explanation is interesting but why oh why &quot;immediate&quot; is thought to be informative escapes me. &nbsp;</p> <p>It is easier for me to grok IIF(c, t, f) as a function that selects one of its operands versus there being a conditional form where evaluation is guided dynamically by the evaluation of c (as in c ? t : f or the ALGOL expression form &quot;if c then t else f&quot; [which nested properly inside of if statements too]). &nbsp;But the &quot;immediate&quot; is weird private language.</p> <p>I guess it depends on what toolcraft you grow up with and what becomes tacitly understood. &nbsp;The term is really not helpful, it seems to me.</p> <p>Do you have more on the history of that?</p> http://blogs.msdn.com/michkap/archive/2007/05/25/2875426.aspx#2970603Tue, 29 May 2007 18:46:55 GMT91d46819-8472-40ad-a661-2c78acb4018c:2970603Michael S. Kaplan<p>Well, at least in Access (where there is an ES to do work), you either wrote a function to do conditional work, or you had an expression with an &nbsp;IIf() -- which is a bit more immediate than writing a separate function.</p> <p>Though that also makes it a bit more &quot;inline&quot; so really either word would have done....</p>