19-05-2025, 04:02 PM
Firstly, the prohibition on std:: strerror was intentional. std:: strerror may not use errno, but can still lead to undefined behaviour.
It was not intended that the rational should be taken an an exhaustive description of issues with all 37 string functions in these headers, rather than an overview.
We could make the rationale more vague, which probably wouldn't help anyone, or make it specify the issues with each of the 37 functions individually. This would make the rationale much much larger for little practical benefit.
It was not intended that the rational should be taken an an exhaustive description of issues with all 37 string functions in these headers, rather than an overview.
We could make the rationale more vague, which probably wouldn't help anyone, or make it specify the issues with each of the 37 functions individually. This would make the rationale much much larger for little practical benefit.
Posted by and on behalf of
the MISRA C++ Working Group
the MISRA C++ Working Group