Explore >> Select a destination
|
You are here 
|
www.cppstories.com | ||
| | | | |
cppstories.com
|
|
| | | | | The C++ Standard Library: A Tutorial and Reference (2nd Edition) by Nicolai M. Josuttis We are still waiting for some more books about new C++ standard. Fortunately for us, some authors managed to write books even before C++11 is well "domesticated". One of such examples is the book mentioned in the title of this post. | |
| | | | |
cppstories.com
|
|
| | | | | The C++ Standard Library: A Tutorial and Reference (2nd Edition) by Nicolai M. Josuttis We are still waiting for some more books about new C++ standard. Fortunately for us, some authors managed to write books even before C++11 is well "domesticated". One of such examples is the book mentioned in the title of this post. | |
| | | | |
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. | |
| | | | |
live-miraculous.pantheonsite.io
|
|
| | | |||
