C# interview

[Jarrett Billingsley]

On Thu, Oct 2, 2008 at 7:25 AM, Ary Borenszweig <ary at esperanto.org.ar> wrote:

> If null references are the most problematic (and I must agree because I
> started a project in D and I got null referneces a few times already, but no
> other "bug"), why is it that in debug mode asserts are not put for every
> reference access, to show "somefile.d(58): Error: Null Reference" instead of
> just "Error: Access Violation"? :-(
>
> No, instead you have to open a debugger to discover the file and line
> number... What's the point of losing that time?
>

Because -- according to Walter -- access violations are much better
than how they had it in the old days before memory protection (back
when programmers had to walk 20 miles uphill both ways in the snow to
work), so you'd better be satisfied with them.

I think it's an awful argument.