how-to
/
CppCoreGuidelines
mirror of https://github.com/isocpp/CppCoreGuidelines.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Typos

Browse Source 
wil => will;
developemnt => development.
pull/515/head
Marat Tanalin 10 years ago
parent 5547b43c4b
commit a67f8d3c27
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

4
CppCoreGuidelines.md
Unescape Escape View File

@ -6946,8 +6946,8 @@ A major class of exception is legacy code, especially code that must remain comp
The fact that there are billions of lines of code that violate this rule against owning `T*`s cannot be ignored. The fact that there are billions of lines of code that violate this rule against owning `T*`s cannot be ignored.
We'd love to see program transformation tools turning 20-year-old "legacy" code into shiny modern code, We'd love to see program transformation tools turning 20-year-old "legacy" code into shiny modern code,
we encourage the development, deploymenta and use of such tools, we encourage the development, deploymenta and use of such tools,
we hope the guidelines wil help the development of such tools, we hope the guidelines will help the development of such tools,
and we even contributed (and contribute) to the research and developemnt in this area. and we even contributed (and contribute) to the research and development in this area.
However, it will take time: "legacy code" is generated faster than we can renovate old code, and so it will be for a few years. However, it will take time: "legacy code" is generated faster than we can renovate old code, and so it will be for a few years.
This code cannot all be rewritten (ever assuming good code transformation software), especially not soon. This code cannot all be rewritten (ever assuming good code transformation software), especially not soon.

Write Preview
Loading…
Cancel
Save