I don't think we are claiming what you say we are claiming. I know I'm only responding because of your claim that you can know what your code does even in the

I don't think we are claiming what you say we are claiming. I know I'm only responding because of your claim that you can know what your code does even in the face of undefined behavior. I think this more accurately describes my position: Code without undefined behavior can absolutely run just fine. Code with undefined behavior is a problem waiting to happen. Code with undefined behavior that happens to run the way you want is a happy accident. The longer it runs correctly the luckier you are. Code in safety systems should not contain undefined behavior. I would encourage everyone to be aware of undefined behavior, get rid of it when they know of it, and take steps to be proactive against it. For code in safety systems I would require these things if it were up to me.