Thanks for the info. Walter and my perception is that safety is big and

first proposing it).<
The purpose of that SAFECode is very different from the purpose of D safe:
it's a tool to help find bugs in unsafe code, while safe merely disallows some
memory-unsafe operations. I presume both things are needed, because sometimes
you need to write unsafe code too. I'd like some optional functionality like
SAFECode in the D compiler too.
Bye,
bearophile

You're not going to use those runtime checks in high performance video code.

I see it as infrastructure useful for debugging and code test. The advantage
over Valgrind is that it doesn't slow down the code 10 times, but only 1.2-1.5
times, so you are able to play the game during debugging too.
Bye,
bearophile

You're not going to use those runtime checks in high performance video code.

I see it as infrastructure useful for debugging and code test. The advantage
over Valgrind is that it doesn't slow down the code 10 times, but only 1.2-1.5
times, so you are able to play the game during debugging too.
Bye,
bearophile

Not to mention while games are performance sensitive, unless it's an
AAA title it's probably not _that_ sensitive in the majority of areas.
Most games are loaded with assertions in debug mode anyway.
Cheers,
Josh