Effective C++ Item 15 Provide access to raw resources in resource-managing classes
2014-02-28 14:33
405 查看
In last two item, I talk about resource-managing using RAII, now comes to the practical part. Often, we encounter a situation where an API accept raw resource instead of RAII object. For example:
In this situation, you need RAII object return raw resources. And there are commonly two ways to do that
1. Explicitly provide method to return raw resource of RAII object. That's how shared_ptr handles this situation. shared_ptr have get() method to return raw resource it contains. In addition, it overload -> and * method. This way is safe and clear, but still some make might think it not natural, and we have a second way to accomplish it.
2. Implicitly convert RAII object to raw resource.
How to do that? Let's see a example
We overload operator () to implicitly convert Font to FontHandle and eliminate the use of get(). But this way have a downside.
If f1 is destroyed and FontHandler is released then f2 become dangle pointer.
// You have a shared pointer std::tr1::shared_ptr<Foo> foo(createFoo()); // But the API only accept Foo void acceptFoo(Foo *foo);
In this situation, you need RAII object return raw resources. And there are commonly two ways to do that
1. Explicitly provide method to return raw resource of RAII object. That's how shared_ptr handles this situation. shared_ptr have get() method to return raw resource it contains. In addition, it overload -> and * method. This way is safe and clear, but still some make might think it not natural, and we have a second way to accomplish it.
2. Implicitly convert RAII object to raw resource.
How to do that? Let's see a example
class Font { public: ... operator FontHandle() const { return f; } private: FontHandle f; };
We overload operator () to implicitly convert Font to FontHandle and eliminate the use of get(). But this way have a downside.
Font f1(getFont()); // oops, intent to copy a Font object, but wrongly write FontHandler // yet implicitly convertion hold the candle to the devil FontHandler f2 = f1;
If f1 is destroyed and FontHandler is released then f2 become dangle pointer.
相关文章推荐
- Item 15: Provide access to raw resources in resource-managing classes.(Effective C++)
- [EffectiveC++]item15:Provide access to raw resources in resource-managing class
- 条款15:在资源管理类中提供对原始资源的访问(Provide access to raw resources in resource-managing classes)
- Effective C++ Item 10,11 Have assignment operators return a reference to *this Handle assignment to self in operator =
- Effective C++ Item 2:Prefer constS, enumS, and inlineS to #defineS
- 读书笔记 effective c++ Item 15 在资源管理类中提供对原生(raw)资源的访问
- 读书笔记 effective c++ Item 15 在资源管理类中提供对原生(raw)资源的访问
- 读书笔记 effective c++ Item 15 在资源管理类中提供对原生(raw)资源的访问
- 读书笔记 effective c++ Item 15 在资源管理类中提供对原生(raw)资源的访问
- Effective C++ Item 14 Think carefully about copying behavior in resource-managing classe
- effective C++ Item 2: Prefer consts, enums, and inlines to #defines
- Effective C++ Item 13 Use object to manage resources
- 读书笔记 effective c++ Item 15 在资源管理类中提供对原生(raw)资源的访问
- Item 43: Know how to access names in templatized base classes(Effective C++)
- 读书笔记 effective c++ Item 15 在资源管理类中提供对原生(raw)资源的访问
- 读书笔记 effective c++ Item 15 在资源管理类中提供对原生(raw)资源的访问
- More Effective C++ 读书摘要(三、异常)Item9 - 15
- What happens when more restrictive access is given to a derived class method in C++?
- Item 2: Prefer consts, enums, and inlines to #defines(Effective C++)
- Item 14: Think carefully about copying behavior in resource-managing classes.(Effective C++)