From c9e015ce1fe27d432b27c8dd598c586db95628fd Mon Sep 17 00:00:00 2001 From: hsutter Date: Tue, 29 Dec 2015 09:29:06 -0800 Subject: [PATCH] Addressed PR 52. --- CppCoreGuidelines.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index ad4f0cc..3c8d7fe 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -13794,9 +13794,9 @@ Thus, we need a way of gradually modernizing a code base. Upgrading older code to modern style can be a daunting task. Often, the old code is both a mess (hard to understand) and working correctly (for the current range of uses). Typically, the original programmer is not around and test cases incomplete. -The fact that the code is a mess dramatically increases to effort needed to make any change and the risk of introducing errors. -Often messy, old code runs unnecessarily slowly because it requires outdated compilers and cannot take advantage of modern hardware. -In many cases, programs support would be required for major upgrade efforts. +The fact that the code is a mess dramatically increases the effort needed to make any change and the risk of introducing errors. +Often, messy old code runs unnecessarily slowly because it requires outdated compilers and cannot take advantage of modern hardware. +In many cases, automated "modernizer"-style tool support would be required for major upgrade efforts. The purpose of modernizing code is to simplify adding new functionality, to ease maintenance, and to increase performance (throughput or latency), and to better utilize modern hardware. Making code "look pretty" or "follow modern style" are not by themselves reasons for change.