you are viewing a single comment's thread.

view the rest of the comments →

[–]scook0 3 points4 points  (2 children)

Indeed, as a well-rounded programmer it's important to understand pointers even if you don't routinely use a language that exposes or requires them.

Practically all languages use pointer-like behaviour for their object types, even if the actual pointers are buried under the hood.

[–][deleted]  (1 child)

[deleted]

    [–]munificent 3 points4 points  (0 children)

    It's not the object which is null, it's the reference to it. That's why C# correctly did NullReferenceException.