Undefined behaviours in D and C

bearophile bearophileHUGS at lycos.com
Thu Apr 15 14:19:57 PDT 2010


Lars T. Kyllingstad:
> The effect of @safe would be to forbid code that leads to undefined 
> behaviour, not make it well-defined.

Right, but that's not the solution I was looking for, and it's not going to solve the problems inherited from C. Because if people that use D want to use unsafe code too, otherwise they use C#/Java. Having safe modules in D is a good idea, but safe modules can't be a replacement for efforts to make safer the low level code too.

Bye,
bearophile



More information about the Digitalmars-d mailing list