I just remember that it crashed if you tried to modify a string literal, which IIRC is undefined. And that it was very diligent about scope.
If you had signed integer over/underflow it wrote insulting error messages.
If you had signed integer over/underflow it wrote insulting error messages.
> He had the wonderful idea of not implementing any undefined behaviour that wasn't strictly necessary
What does this mean? It sounds like the way an ordinary C compiler works: it ignores the possibility of undefined behaviour occurring, as the C standard allows it to do this.