Ерунда какая-то написана. Исключения никак не влияют на realtime, в худшем случае только на производительность программы.
Под realtime я понимаю гарантированное время исполнения. Herb Sutter пишет (
http://www.open-std.org/jtc1/sc22/wg21/ ... 0709r0.pdf)
Цитата:
(2) Today’s dynamic exception handling is not deterministic (run-time space and time determinism). This is the primary reason exceptions are banned in many real-time and/or safety-critical environments (for example, many games, coding standards like JSF++ [JSF++ 2005], and environments like the Mars Rover flight software [Maimone 2014]). C++ allows there to be multiple active exception objects of arbitrary types, which must have unique addresses and cannot be folded; and it requires using RTTI to match handlers at run time, which has statically unpredictable cost on all major implementations and can depend on what else is linked into the whole program. Therefore during stack unwinding the exception handling space and time cost is not predictable as it is with error codes. Adequate tools do not exist to statically calculate upper bounds on the actual costs of throwing an exception.
Цитата:
We know that today’s dynamic exception model has inherent overheads with no known solution for common and important cases such as memory-constrained and/or real-time systems, which require deterministic space and/or time cost of throwing an exception, with a statically computable upper bound on those costs. For space determinism (memory-constrained systems), I am not aware of any research progress in the past decade. For time determinism (real-time systems), proponents of today’s dynamic exceptions expected suitability for realtime systems to be achieved before 2010; but, as noted in §2.3, there have been only a handful of research results (all over a decade old), notably [Gibbs 2005] which unfortunately is not suitable for general use because of its restrictions on the sizes of class hierarchies and reliance on static linking.
