Explore >> Select a destination
|
You are here 
|
blog.httrack.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. | |
| | | | |
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. | |
| | | | |
blog.oddbit.com
|
|
| | | | | Overview I was recently working with someone else's C source and I wanted to add some basic error checking without mucking up the code with a bunch of if statements and calls to perror. I ended up implementing a simple must function that checks the return value of an expression, and exits with an error if the return value is less than 0. You use it like this: must(fd = open("textfile.txt", O_RDONLY)); Or: | |
| | | | |
mklimenko.github.io
|
|
| | | Every time I work with a C library, I miss the power and capability of the type system C++ provides. That's why I developed a simple C++17 header-only helper library to pack the multiple type-dependent C-style functions into single overload deduced at compile-time. No external libraries are required. Repo link: https://github.com/MKlimenko/plusifier. Currently, it's just the header and a compile-time test file, CMake integration coming soon. | ||
