在 C 或 C++ 中，我应该根据 NULL/nullptr 检查指针参数吗?
这个问题的灵感来自 这个答案.
This question was inspired by this answer.
我一直认为，当调用者做了一些愚蠢的事情时，被调用者从不负责，比如传递无效参数.我得出这个结论有几个原因，但也许最重要的一个来自 这篇文章:
I've always been of the philosophy that the callee is never responsible when the caller does something stupid, like passing of invalid parameters. I have arrived at this conclusion for several reasons, but perhaps the most important one comes from this article:
未定义的都是未定义的.
Everything not defined is undefined.
如果一个函数在它的文档中没有说传递 nullptr 是有效的，那么你最好不要将 nullptr 传递给该函数.我认为处理这种事情不是被调用者的责任.
If a function doesn't say in it's docs that it's valid to pass nullptr, then you damn well better not be passing nullptr to that function. I don't think it's the responsibility of the callee to deal with such things.
但是，我知道会有一些人不同意我的观点.我很好奇我是否应该检查这些东西，以及为什么.
However, I know there are going to be some who disagree with me. I'm curious whether or not I should be checking for these things, and why.
推荐答案
虽然一般来说我看不到公共 API 检测 NULL 的价值(为什么是 NULL 而不是其他无效地址?)这样做只是因为许多 C 和 C++ 程序员期望这种行为.
While in general I don't see the value in detecting NULL (why NULL and not some other invalid address?) for a public API I'd probably still do it simply because many C and C++ programmers expect such behavior.
相关文章