![]() ![]() ![]() Such rules affect application architecture and library design.įollowing the rules will lead to code that is statically type safe, has no resource leaks, and catches many more programming logic errors than is common in code today.Īnd it will run fast – you can afford to do things right. The guidelines are focused on relatively high-level issues, such as interfaces, resource management, memory management, and concurrency. In other words, what would you like your code to look like in 5 years’ time, given that you can start now? In 10 years’ time? The aim of this document is to help people to use modern C++ effectively.īy “modern C++” we mean effective use of the ISO C++ standard (currently C++17, but almost all of our recommendations also apply to C++14 and C++11). This document is a set of guidelines for using C++ well. You can look at design concepts used to express the rules: You can sample rules for specific language features: FAQ: Answers to frequently asked questions.You can read an explanation of the scope and structure of this Guide or just jump straight in: For a more-or-less up-to-date to-do list see: To-do: Unclassified proto-rules.Update reference sections many pre-C++11 sources are too old. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |