but this power brings with it complexity, which in turn can make code more bug-prone and harder to read and maintain. The goal of this guide is to manage this complexity by describing in detail the dos tricky or hard to maintain C++ has features that may not be generally appropriate because of the complexity they introduce to the code. In widely used code, it may be 2 more acceptable to use trickier of more complex implementation are multiplied widely by usage, and the cost in understanding the complexity does not need to be paid again when working with new portions of the codebase. When in doubt, waivers

paper solving the problem?  Is this the simplest approach that yields these results (justified complexity)  Are there limitations that are not covered by the paper?  Is there existing work that already

access the variable by the old method should break visibly so they are made aware of the change in complexity. Naming link￿ module_name, package_name, ClassName, method_name, ExceptionName, function_name