Modern C/C++ programming prefers perror() or returning error values, to using assert(). I understand this is because assert() often becomes a NOP in release binaries, and assert() can occasionally leak sensitive information.
Given that assert() is now frowned upon, could splint update its rule checks to recommend suitable replacements in our source code files?