Reply to thread

Message: [QUOTE="Frank Puck, post: 1478475"] Being aware of that certain statements may throw and writing code, which does not ignore this fact. Writing code that relies on the fact that it will only be executed if and only if all previous statements have executed successfully. Matching design philosophies including e.g. * the notion of non-corrupting fail of an operation * the notion that the enduser can expect to see a descriptive error message, which includes any system error message and maybe even stack-trace information, e.g.: Cannot parse input file "test.cpp", because of Cannot start preprocessor, because of maximum number of processes reached so you ignore that new may throw? so you ignore that opening a file for writing may fail? assertions are still useful [/QUOTE]