Explore >> Select a destination
|
You are here 
|
cppstories.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. | |
| | | | |
eyakubovich.github.io
|
|
| | | | | The guidance around function arguments and smart pointers is quite old, yet I still see it used incorrectly. In this post, we'll explore the guidance and the costs of not following the advice. C++ Core Guidelines make this point clear: F.7: For general use, take T* or T& arguments rather... | |
| | | | |
modexp.wordpress.com
|
|
| | | | | Introduction Quick post about Windows System calls that I forgot about working on after the release of Dumpert by Cn33liz last year, which is described in this post. Typically, EDR and AV set hooks on Win32 API or NT wrapper functions to detect and mitigate against malicious activity. Dumpert attempts to bypass any user-level hooks... | |
| | | | |
ponyfoo.com
|
|
| | | |||
