openharmony-cpp

Secure coding for OpenHarmony C++ requires mandatory input validation, integer safety, and memory-safety practices like nulling pointers after deletion. It enforces strict rules for file extensions, conventional include guards instead of #pragma once, and specific C++ design constraints to prevent security defects.

To review OpenHarmony C++ code, check headers and source files against naming and formatting rules like K&R braces, file alignment, and variable prefixes. You must verify header scope rules, conventional include guards, and secure coding practices to report every violation found during refactoring.

OpenHarmony C++ discourages using #pragma once for header guards. The conventions require conventional include guards instead, actively discouraging forward-declaration hiding and header pollution to ensure safe header management across platform modules.

C++ design constraints for OpenHarmony guide modern usage including explicit constructors, nullptr, and override specifiers. They enforce constructor and destructor rules alongside reasonable function size and parameter limits to maintain class and function design quality.

Standard C++ memory practices must be tightened for OpenHarmony modules by enforcing memory-safety behaviors. This includes specific actions like nulling pointers after deletion and applying integer safety rules to prevent common robustness defects and security vulnerabilities.

OpenHarmony C++ code fails security review without strict header management because fragile headers and header pollution introduce avoidable security bugs. Enforcing conventional include guards and preventing forward-declaration hiding reduces this security review risk significantly.