C++ 设计篇之——pimpl 机制

源码仓库：https://github.com/yeshenyong/practice_cpp/tree/master/pimpl

Pointer to implementation（PImpl ），通过将类的实现细节放在一个单独的类中，从其对象表示中删除它们，通过一个不透明的指针访问它们（cppreference 是这么说的）

通过一个私有的成员指针，将指针所指向的类的内部实现数据进行隐藏

class Demo {
public:
	...
private:
	DemoImp* imp_;
}

个人拙见

1. C++ 不像Java 后端型代码，能有行业定式的列目录名形成规范（controller、Dao等）
2. 隐藏实现，降低耦合性和分离接口（隐藏类的具体实现）
3. 通过编译期的封装（隐藏实现类的细节）

业界实现

1. 优秀开源代码有实现

cook_cuisine.h

#pragma once

#include 
#include 
#include 

//  Pointer to impl ementation

class CookImpl;

// 后厨
class Cook {

public:
    Cook(int, const std::vector&);
    ~Cook();
    std::vector getMenu();     
    uint32_t getChefNum();                  

private:
    CookImpl* impl_;
};
typedef std::shared_ptr CookPtr;		// 美妙的typedef 懒人工具

cook_cuisine.cc

#include "cook_cuisine.h"

class CookImpl {
public:
    CookImpl(uint32_t checf_num, const std::vector& menu):checf_num_(checf_num), menu_(menu) {}
    std::vector getMenu();
    uint32_t getChefNum();

private:
    uint32_t checf_num_;
    std::vector menu_;
};

std::vector CookImpl::getMenu() {
    return menu_;
}

uint32_t CookImpl::getChefNum() {
    return checf_num_;
}

Cook::Cook(int chef_num, const std::vector& menu) {
    impl_ = new CookImpl(chef_num, menu);
}

Cook::~Cook() {
    delete impl_;
}

std::vector Cook::getMenu() {
    return impl_->getMenu();
}

uint32_t Cook::getChefNum() {
    return impl_->getChefNum();
}

cook_cuisine.h

#pragma once

#include 
#include 
#include 

#include "cook_cuisine_imp.h"

// 后厨
class Cook {

public:
    Cook(int, const std::vector&);
    ~Cook();
    std::vector getMenu();     
    uint32_t getChefNum();                  

private:
    CookImplPtr impl_;
};
typedef std::shared_ptr CookPtr;

cook_cuisine.cc

#include "cook_cuisine.h"

Cook::Cook(int chef_num, const std::vector& menu) {
    impl_.reset(new CookImpl(chef_num, menu));
}

Cook::~Cook() {
    
}

std::vector Cook::getMenu() {
    return impl_->getMenu();
}

uint32_t Cook::getChefNum() {
    return impl_->getChefNum();
}

cook_cuisine_imp.h

#pragma once

#include 
#include 
#include 


class CookImpl {
public:
    CookImpl(uint32_t checf_num, const std::vector& menu):checf_num_(checf_num), menu_(menu) {}
    std::vector getMenu();
    uint32_t getChefNum();

private:
    uint32_t checf_num_;
    std::vector menu_;
};
typedef std::shared_ptr CookImplPtr;

cook_cusine_imp.cc

#include "cook_cuisine_imp.h"

std::vector CookImpl::getMenu() {
    return menu_;
}

uint32_t CookImpl::getChefNum() {
    return checf_num_;
}

main.cc

#include "cook_cuisine.h"
#include 


using namespace std;    // Testing, 平时开发可千万别用这句

int main() {
    int checf_num = 10;
    const std::vector menus = { "Chicken", "Beef", "Noodle", "Milk" };
    CookPtr cook(new Cook(checf_num, menus));

    auto cook_menu = cook->getMenu();
    auto cook_checf_num = cook->getChefNum();

    cout << "======================Chinese Cook======================n";

    cout << "============Checf: " << cook_checf_num << " peoplen";

    cout << "==========Menun";

    for (size_t i = 0; i < cook_menu.size(); i++) {
        cout << "============" << i + 1 << " : " << cook_menu[i] << "n";
    }

    return 0;
}

CMakeLists.txt

mkdir build
cd build
cmake ..

1. 空间开销：每个类都需要额外的指针内存指向实现类
2. 时间开销：每个类间接访问实现的时候多一个间接指针操作的开销
3. 阅读开销：使用、阅读和调试上带来一些不便（不是啥问题）

每种设计方法都有它的优点和缺点

PImpl 用一些内存空间和额外类的实现换取耦合性的下降，是可以接受的

但重点在：在性能/内存要求不敏感处，PImpl 技术才更优不错的发挥舞台

极端例子：

你不可能在斐波那契的实现中还加个PImpl 机制，多此一举