100 C++ Mistakes and How to Avoid Them

English | 2025 | ISBN: 978-1633436893 | 360 Pages | EPUB | 10 MB

Learn how to handle errors, inefficiencies, and outdated paradigms by exploring the most common mistakes you’ll find in production C++ code.

100 C++ Mistakes and How To Avoid Them reveals the problems you’ll inevitably encounter as you write new C++ code and diagnose legacy applications, along with practical techniques you need to resolve them.

Inside 100 C++ Mistakes and How To Avoid Them you’ll learn how to:

• Design solid classes
• Minimize resource allocation/deallocation issues
• Use new C++ features
• Identify the differences between compile and runtime issues
• Recognize C-style idioms that miss C++ functionality
• Use exceptions well

100 C++ Mistakes and How To Avoid Them gives you practical insights and techniques to improve your C++ coding kung fu. Author Rich Yonts has been using C++ since its invention in the 1980s. This book distills that experience into practical, reusable advice on how C++ programmers at any skill level can improve their code. Unlike many C++ books that concentrate on language theory and toy exercises, this book is loaded with real examples from production codebases.

Over ten billion lines of C++ code are running in production applications, and 98-developers find and fix mistakes in them every day. Even mission-critical applications have bugs, performance inefficiencies, and readability problems. This book will help you identify them in the code you’re maintaining and avoid them in the code you’re writing.

100 C++ Mistakes and How To Avoid Them presents practical techniques to improve C++ code, from legacy applications to modern codebases that use C++ 11 and beyond. Author Rich Yonts provides a concrete example to illustrate each issue, along with a step-by-step walkthrough for improving readability, effectiveness, and performance. Along the way, you’ll even learn how and where to replace outdated patterns and idioms with modern C++.

What’s inside

• Design solid classes
• Resource allocation/deallocation issues
• Compile and runtime problems
• Replace C-style idioms with proper C++