Explore >> Select a destination
|
You are here 
|
meetingcpp.com | ||
| | | | |
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. | |
| | | | |
gpfault.net
|
|
| | | | | ||
| | | | |
brevzin.github.io
|
|
| | | | | Several years ago, I wrote a post about the complexities of implementing comparison operators for optional: Getting in trouble with mixed comparisons. That post was all about how, even just for ==, making a few seemingly straightforward decisions leads to an ambiguity that different libraries handle differently. | |
| | | | |
fsharpforfunandprofit.com
|
|
| | | |||
