Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • “C# is taking steps away from null references.” What steps are those? I haven't seen anything like that in the changes to the language. Or do you mean just that the common libraries are using null less than they did in the past? Commented Dec 15, 2013 at 15:40
  • @svick Bad phrasing on my part. “C# is a mainstream language that has introduced language-level tools to better handle nulls” – I am talking about Nullable types and the ?? default operator. It doesn't solve the problem right now in the presence of legacy code, but it is a step towards a better future. Commented Dec 15, 2013 at 15:46
  • I aggree with you. I would vote up your answer but I don't have enought reputation :( However, Nullable works only for primitive types. So it is just a little step. Commented Dec 15, 2013 at 15:54
  • 1
    @svick Nullable has nothing to do with this. We are talking about all reference types implicitly allowing null value, instead of having programmer define it explicitly. And Nullable can only be used on value types. Commented Dec 15, 2013 at 15:57
  • @Euphoric I think your comment was meant as a reply to amon, I didn't mention Nullable. Commented Dec 15, 2013 at 16:00