tag:blogger.com,1999:blog-26619214.post467642660088665462..comments2010-07-01T00:32:55.727-04:00Annhttp://www.blogger.com/profile/04912097426262293763noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-26619214.post-46349825972981290772010-07-01T00:32:55.721-04:002010-07-01T00:32:55.721-04:00True that... I actually avoided that call... &#39;null&#39;.ExtensionMethod for a while because of my NPE exception fear.<br /><br />In reality, it&#39;s another one of the syntactic sugar calls that C# has and Java needs, along with &#39;var&#39; =&#39;&#39;&#39;(Stevehttp://www.blogger.com/profile/06609172873690727496noreply@blogger.comtag:blogger.com,1999:blog-26619214.post-5580022161945930122010-06-29T11:52:14.085-04:002010-06-29T11:52:14.085-04:00Oh, I would agree: in the majority of cases, throwing an exception when a null object is passed to an extension method makes sense. But it&#39;s interesting and worth knowing that the runtime itself doesn&#39;t automatically throw one.Annhttp://www.blogger.com/profile/08065015354819397934noreply@blogger.comtag:blogger.com,1999:blog-26619214.post-28684787294234253352010-06-29T11:46:44.189-04:002010-06-29T11:46:44.189-04:00From what I have seen, &#39;most&#39; (used loosely) people I have talked to say that passing null into an extension method should always throw a NullRef... but for String functions... it really helps a lot. +1 to you Ann!Stevehttp://www.blogger.com/profile/06609172873690727496noreply@blogger.com