On Sat, 08 Nov 2014 11:46:16 +0000
Nikolay via Digitalmars-d-learn <[email protected]>
wrote:

> > i also developed a habit of writing assert()s before 
> > dereferencing
> > pointers first time (including class refs) in appropriate 
> > places, so
> > i'll got that stack trace for free. ;-) and i never turning off 
> > that
> > asserts in "release builds".
> 
> If we can't rely on system level may be we should have internal 
> check for null deref like for array bounds?
my memory can cheat me, but i bet that this was discussed before and
Walter is against it.

Attachment: signature.asc
Description: PGP signature

Reply via email to