From a4753e240100e2ff7d5be54dfe4ac1cbe2d40196 Mon Sep 17 00:00:00 2001 From: insideoutclub Date: Sat, 4 Mar 2017 06:42:23 -0800 Subject: [PATCH] Update eliminate_runtime_penalty.xml --- doc/boostbook/eliminate_runtime_penalty.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/boostbook/eliminate_runtime_penalty.xml b/doc/boostbook/eliminate_runtime_penalty.xml index b71e5df..d8be0c9 100644 --- a/doc/boostbook/eliminate_runtime_penalty.xml +++ b/doc/boostbook/eliminate_runtime_penalty.xml @@ -7,7 +7,7 @@ Up until now, we've focused on detecting when incorrect results are produced and handling these occurrences either by throwing an exception or invoking some designated function. We've achieved our goal of detecting and - handling arithmetically incorrect behavior - but at what cost. It is a fact + handling arithmetically incorrect behavior - but at what cost? It is a fact that many C++ programmers will find this trade-off unacceptable. So the question arises as to how we might minimize or eliminate this runtime penalty.