Why not implement deep copy in default copy constructor?

Why not implement deep copy in default copy constructor?

http://stackoverflow.com/questions/37640541/why-not-implement-deep-copy-in-default-copy-constructor

All people keep remind us of the case when using default copy constructor and default assign operator, be careful since they’re shadow copy. However, I am always confused why not make deep copy by default among default copy constructor and default assign operator in c++, so that no one need to write their own copy constructor implementation in order to prevent any accident?

C++ implement copy by value, which means it basically does x = y;. In many cases this is enough.

However, in the case of pointers the compiler knows nothing about what is pointed to. It will copy the value of the pointer, but will not duplicate the underlying item because of this. For example, if you’ve got a class like this:

class Foo
{
char *data;
};
Then what should the compiler do with data? It doesn’t know if it points to a single char or an array of char. It doesn’t know anything about how the memory was allocated or how it should be freed. It doesn’t know if it should make a copy, or if all instances of Foo should point to the same instance.

Because of this the language takes a perfectly reasonable default stance, which is that only the value of the pointer will be copied. If you want anything more then you have to do it yourself as only you fully understand the use-case of the variable.

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值