Bad array indexing is considered deadly

Kagamin via Digitalmars-d digitalmars-d at puremagic.com
Thu Jun 1 03:11:19 PDT 2017


On Wednesday, 31 May 2017 at 21:00:43 UTC, Steven Schveighoffer 
wrote:
> To be blunt, no this is completely wrong. Memory corruption 
> *already having happened* can cause any number of errors. The 
> point of bounds checking is to prevent memory corruption in the 
> first place.

Sad reality is that d programmers are still comfortable writing 
code in 70s style playing with void* pointers and don't enable 
bound checks early enough, see 
https://issues.dlang.org/show_bug.cgi?id=13367


More information about the Digitalmars-d mailing list