Explore >> Select a destination
|
You are here 
|
danielsieger.com | ||
| | | | |
www.bfilipek.com
|
|
| | | | | Some time ago I covered how to use custom deleters with smart pointers. The basic idea is to specify a dedicated method that will be called when a pointer is released. One logical application of custom deleters might be resource handles like files or the WinApi HANDLE type. Lets see how can we implement such thing. | |
| | | | |
philjordan.eu
|
|
| | | | | ||
| | | | |
www.cppstories.com
|
|
| | | | | Let's say we have the following code: LegacyList* pMyList = new LegacyList(); ... pMyList->ReleaseElements(); delete pMyList; In order to fully delete an object we need to do some additional action. How to make it more C++11? How to use unique_ptr or shared_ptr here? Intro We all know that smart pointers are really nice things and we should be using them instead of raw new and delete. | |
| | | | |
blogs.remobjects.com
|
|
| | | New users coming fresh to Elements are often wondering how the compiler is able to mix different programming languages, or how it ends up that you can use the same language on different platforms ("doesn't C# only work on .NET?"). Here's how it works. Elements is not made up of | ||
