m15-anti-pattern

To fix C++ anti-patterns, replace raw new/delete and C-style casts with smart pointers, standard containers, static_cast, and constexpr. This refactoring eliminates memory leaks and undefined behavior while preserving compilation during modernization workflows.

Common C++ anti-patterns include raw new/delete, owning raw pointers, C-style casts, void pointers, macros, and global state. These introduce memory leaks, undefined behavior, and brittle code, degrading maintainability and testability across the codebase.

Replace C-style casts and void pointers with static_cast, constexpr, and template-based solutions. These modern C++ alternatives provide type safety, eliminate undefined behavior risks, and make refactoring safer while maintaining compile-preserving behavior.

Yes, anti-pattern detection applies to C++ codebases from small to large projects. It supports code reviews, refactoring sprints, and static analysis workflows to convert legacy modules to modern C++ idioms and remove global state for improved testability.

Removing global state improves testability and lifetime management in C++ codebases. Replacing global variables with dependency injection patterns ensures safer, more maintainable code and eliminates brittle dependencies during refactoring and modernization efforts.

The best way to refactor C++ macros is replacing them with constexpr and template-based solutions. These modern alternatives provide type safety, better debugging capabilities, and eliminate the brittle behavior macros introduce while preserving compilation.