compilation firewalls

探讨C++中使用透明指针隐藏类实现细节的方法,分析不同封装策略的优缺点,包括将私有数据、成员及函数分别放入内部类XImpl中的影响。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

// In C++, when anything in a class definition changes (even private members), 
// all users of that class must be recompiled. To reduce these dependencies, 
// a common technique is to use an opaque pointer to hide some of the implementation details.


class X 
{	
public:
	/* ... public members ... */	
protected:	
	/* ... protected members? ... */	
private:	
	/* ... private members? ... */	
	struct XImpl;	
	XImpl* pimpl_;         // opaque pointer to	
	// forward-declared class	
};

// The questions for you to answer are:
// What should go into XImpl? There are four common disciplines.
// 1.Put all private data (but not functions) into XImpl.
// 2.Put all private members into XImpl.
// 3.Put all private and protected members into XImpl.
// 4.Make XImpl entirely the class that X would have been, 
//   and write X as only the public interface made up entirely of simple forwarding functions (a handle/body variant).
// What are the advantages/drawbacks of each? How would you choose among them?
// Does XImpl require a pointer back to the X object?

// Option 1 (Score: 6 / 10): Put all private data (but not functions) into XImpl. 
// Option 2 (Score: 10 / 10): Put all nonvirtual private members into XImpl. 

// Virtual functions should normally be private,


评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值