本文介绍了在堆栈上分配的变量上调用 delete的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
忽略编程风格和设计，对分配在堆栈上的变量调用 delete 是否安全"?
Ignoring programming style and design, is it "safe" to call delete on a variable allocated on the stack?
例如:
int nAmount;
delete &nAmount;
或
class sample
{
public:
sample();
~sample() { delete &nAmount;}
int nAmount;
}
推荐答案
否，在堆栈分配的变量上调用 delete 是不安全的.你应该只对 new 创建的东西调用 delete.
No, it is not safe to call delete on a stack-allocated variable. You should only call delete on things created by new.
- 对于每个
malloc或calloc，应该只有一个free. - 对于每个
new，应该恰好有一个delete. - 对于每个
new[]，应该恰好有一个delete[]. - 对于每个堆栈分配，不应有明确的释放或删除.在适用的情况下，会自动调用析构函数.
- For each
mallocorcalloc, there should be exactly onefree. - For each
newthere should be exactly onedelete. - For each
new[]there should be exactly onedelete[]. - For each stack allocation, there should be no explicit freeing or deletion. The destructor is called automatically, where applicable.
一般情况下，您不能混合搭配其中任何一种，例如没有 free-ing 或 delete[]-ing new 对象.这样做会导致未定义的行为.
In general, you cannot mix and match any of these, e.g. no free-ing or delete[]-ing a new object. Doing so results in undefined behavior.
这篇关于在堆栈上分配的变量上调用 delete的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！
本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除！