Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Refactoring with C++

You're reading from   Refactoring with C++ Explore modern ways of developing maintainable and efficient applications

Arrow left icon
Product type Paperback
Published in Jul 2024
Publisher Packt
ISBN-13 9781837633777
Length 368 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Mr. Dmitry Danilov Mr. Dmitry Danilov
Author Profile Icon Mr. Dmitry Danilov
Mr. Dmitry Danilov
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Chapter 1: Coding Standards in C++ 2. Chapter 2: Main Software Development Principles FREE CHAPTER 3. Chapter 3: Causes of Bad Code 4. Chapter 4: Identifying Ideal Candidates for Rewriting – Patterns and Anti-Patterns 5. Chapter 5: The Significance of Naming 6. Chapter 6: Utilizing a Rich Static Type System in C++ 7. Chapter 7: Classes, Objects, and OOP in C++ 8. Chapter 8: Designing and Developing APIs in C++ 9. Chapter 9: Code Formatting and Naming Conventions 10. Chapter 10: Introduction to Static Analysis in C++ 11. Chapter 11: Dynamic Analysis 12. Chapter 12: Testing 13. Chapter 13: Modern Approach to Managing Third Parties 14. Chapter 14: Version Control 15. Chapter 15: Code Review 16. Index 17. Other Books You May Enjoy

The essence of static analysis

Static analysis is the examination of source code without executing it. This process, typically automated by various tools, involves scanning the code to identify potential errors, code smells, security vulnerabilities, and other issues. It’s akin to a thorough proofreading session where the code is scrutinized for quality and reliability before it ever runs.

Why static analysis? Here are the reasons:

  • Speed and cost-effectiveness: The foremost advantage of static analysis is its speed and cost-effectiveness. It is arguably the fastest and cheapest method to find bugs. Automating the detection of issues drastically reduces the time and effort required compared to manual code reviews and other testing methods. Catching and resolving issues early in the development cycle significantly lowers the cost of fixes, which escalates if bugs are found later in production.
  • Pre-execution bug detection: Static analysis occurs before the code is...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image