CompuServe Messages

They do not "purposely" violate. If I can avoid it without hurting performance, then I'll do it. I see Range-Checking to be useful as a safeguard when developing software, once the software is done, the checking is no longer needed. Since I know how the compiler does stuff and how the M2Sprint environment behaves, I know I can afford to do slight range checking errors to improve performance. If the compiler' behavior changes, I can change the modules. This works well cause I provide both the compiler and the modules. It might not be so easy for a normal user to do though.