条款46宁可编译和链接时出错,也不要运行时出错（Clause 46 compile and link errors rather than run errors）.docVIP

条款46宁可编译和链接时出错,也不要运行时出错（Clause 46 compile and link errors rather than run errors） Clause 46: error when compiling and linking, and do not run error Except for very few cases where C++ throws exceptions (for example, memory is exhausted - see clause 7), the concept of runtime error has nothing to do with C++, as in C. No overflow, underflow, except the zero check; no array bounds check, etc.. Once the program has been compiled and linked, you have to rely on yourself - - all consequences. Its like skydiving. Some people find it exciting, while others are crippled by fright. The motivation behind this idea is, of course, efficiency: without running checks, the program will be smaller and faster. Theres a different way of dealing with this kind of thing. Some languages, such as Smalltalk and LISP, usually check very few errors during compile links, but provide a powerful runtime system for handling errors during execution. Unlike C++, these languages are almost interpreted, providing performance flexibility as well as providing additional flexibility. Dont forget that you are programming with C++. Even if Smalltalk/LISPs approach is attractive, forget about them. It is often said that we must adhere to the partys line and, in the present case, its implication is to avoid run-time errors. Whenever possible, let the error check go back from the runtime to the link, or, ideally, at compile time. The benefits of this approach lie not only in the size and speed of the program, but also in reliability. If the program compiles and links, no error information is generated, You can be sure that no compiler and linker in the program can check for any errors, and thats all. (of course, another possibility is that the compiler or linker has problems, but dont bother us with that possibility.) The situation is quite different for runtime errors. During a run, the program does not produce any runtime errors, so you can be sure that another different run period will not cause errors?