是否有任何理由在删除之前检查 NULL 指针?

Is there any reason to check for a NULL pointer before deleting?(是否有任何理由在删除之前检查 NULL 指针?)
本文介绍了是否有任何理由在删除之前检查 NULL 指针?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

问题描述

我经常看到遗留代码在删除指针之前检查NULL,类似于,

I often see legacy code checking for NULL before deleting a pointer, similar to,

if (NULL != pSomeObject) 
{
    delete pSomeObject;
    pSomeObject = NULL;
}

是否有任何理由在删除之前检查 NULL 指针?之后将指针设置为NULL的原因是什么?

Is there any reason to checking for a NULL pointer before deleting it? What is the reason for setting the pointer to NULL afterwards?

推荐答案

删除空指针是完全安全"的;它实际上相当于一个空操作.

It's perfectly "safe" to delete a null pointer; it effectively amounts to a no-op.

您可能希望在删除之前检查 null 的原因是尝试删除空指针可能表明您的程序中存在错误.

The reason you might want to check for null before you delete is that trying to delete a null pointer could indicate a bug in your program.

编辑

注意:如果重载删除操作符,删除NULL

NOTE: if you overload the delete operator, it may no longer be "safe" to delete NULL

这篇关于是否有任何理由在删除之前检查 NULL 指针?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

相关文档推荐

Unable to access non-const member functions of objects in C++ std::set(无法访问 C++ std::set 中对象的非常量成员函数)
Constructing std::function argument from lambda(从 lambda 构造 std::function 参数)
STL BigInt class implementation(STL BigInt 类实现)
Sync is unreliable using std::atomic and std::condition_variable(使用 std::atomic 和 std::condition_variable 同步不可靠)
Move list element to the end in STL(在 STL 中将列表元素移动到末尾)
Why is overloading operatoramp;() prohibited for classes stored in STL containers?(为什么禁止对存储在 STL 容器中的类重载 operatoramp;()?)