Explore >> Select a destination
|
You are here 
|
duerrenberger.dev | ||
| | | | |
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. | |
| | | | |
cppstories.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. Let's see how can we implement such thing. | |
| | | | |
www.fraknoi.com
|
|
| | | | | Suggestions for how best to view the Perseid meteor shower, which is one of the best displays of shooting stars in the course of the year. | |
| | | | |
binarydebt.wordpress.com
|
|
| | | System call table is an array of function pointers. It is defined in kernel space as variable sys_call_table and it contains pointers to functions which implement system calls. Index of each function pointer in the array is the system call number for that syscall. These are denoted by NR_* macros in header files, such as... | ||
