C++ Strange constructor behaviour(C++ 奇怪的构造函数行为)
问题描述
谁能给我解释一下Complex a;和Complex b();之间的区别吗?
Can anybody explain to me the difference between Complex a; and Complex b();?
#include<iostream>
class Complex
{
public:
Complex()
{
std::cout << "Complex Constructor 1" << std::endl;
}
Complex(float re, float im)
{
std::cout << "Complex Constructor 2" << std::endl;
}
~Complex()
{
std::cout << "Complex Destructor" << std::endl;
}
};
int main()
{
Complex a;
std::cout << "--------------------------" << std::endl;
Complex b();
std::cout << "--------------------------" << std::endl;
Complex c(0,0);
std::cout << "--------------------------" << std::endl;
return 0;
}
输出:
Complex Constructor 1
--------------------------
--------------------------
Complex Constructor 2
--------------------------
Complex Destructor
Complex Destructor
如您所见,Complex a; 确实调用了它的默认构造函数,Complex b(); 没有,Complex c(0,0); 调用重载的构造函数.
As you can see, Complex a; does call its default constructor, Complex b(); doesn't and Complex c(0,0); calls an overloaded constructor.
这里发生了什么?我想,Complex b(); 会创建一个堆栈变量并调用它的默认构造函数来初始化它?
What is going on here? I thought, that Complex b(); would create a stack-variable and call it's default constructor to initialize it?
推荐答案
Complex b(); 是函数声明.这是不带参数并返回 Complex 对象的函数.
Complex b(); is function declaration. That is function taking no arguments and returning Complex object.
这是一个很常见的错误并且有自己的名字:最令人头疼的解析
This is very common mistake and has its own name: most vexing parse
C++11 通过引入统一初始化语法帮助解决了这个问题
C++11 helped with this issue by introducing uniform initialization syntax
Complex b{};
这篇关于C++ 奇怪的构造函数行为的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:C++ 奇怪的构造函数行为
基础教程推荐
- c++ STL设置差异 2022-01-01
- 提升 ASIO 流缓冲 2021-01-01
- 为什么我们不能使用“虚拟继承"?在 COM 中? 2022-01-01
- 如何在 C++ 中正确使用命名空间? 2022-01-01
- 将不可复制的闭包对象传递给 std::function 参数 2021-01-01
- 如何更改 SysDateTimePick32 或 CDateTimeCtrl 的背景颜色? 2022-01-01
- 与 CAS 的原子交换(使用 gcc 同步内置函数) 2022-01-01
- 如何部分禁用 cmake C/C++ 自定义编译器检查 2021-01-01
- 随机插入/删除的综合向量与链表基准 2022-01-01
- C++:获取传递给函数的多维数组的行大小 2021-01-01
