dereferencing null

[Nick Sabalausky]

"Walter Bright" <newshound2 at digitalmars.com> wrote in message 
news:jj252v$15vf$1 at digitalmars.com...
> On 3/4/2012 11:50 PM, Chad J wrote:
>> Problems:
>> - I have to rerun the program in a debugger to see the stack trace. This 
>> is a
>> slow workflow. It's a big improvement if the segfault is hard to find, 
>> but only
>> a small improvement if the segfault is easy to find. Very bad if I'm 
>> prototyping
>> experimental code and I have a bunch to go through.
>
> I don't get this at all. I find it trivial to run the program with a 
> debugger:
>
>   gdb foo
>   >run
>
> that's it.
>

Not all software is minimally-interactive CLI.

>> I'm pretty sure other languages like C# and Java get this right. Haven't 
>> used
>> those two in a while though. Haxe... totally got this right. Also 
>> Actionscript 3
>> by proxy. Hell, even Synergy/DE, the DIBOL (!!) derivative that I use at 
>> work,
>> /gets this right/. I get stacktraces for null dereferences in these 
>> languages.
>> It's /really/ convenient and useful. I consider D to be very backwards in 
>> this
>> regard.
>
> Notably, C and C++ do not do what you suggest.

So what? C and C++ suck ass. That's why D exists.