[MECpp]Item-3 Never Treat Arrays Polymorphically
· β 3 min read
Array operations almost always involve pointer arithmetic, so arrays and polymorphism don’t mix.
technique
[MECpp]Item-1 Distinguish Between Pointers and References
· β 3 min read
More effective C++: Use references when we already have something to refer to and never want to refer to anything else, or when implementing operators whose syntactic requires us to do so.
Item-52 Write placement delete if you write placement new
· β 5 min read
When we write a placement version of operator new, be sure to write the corresponding placement version of operator delete to avoid subtle, intermittent memory leaks. When we do so, pay attention not to unintentionally hide the normal versions of new and delete
Item-51 Adhere to convention when writing new and delete
· β 4 min read
operator new should contain an infinite loop trying to allocate memory, should call the new-handler if it can’t satisfy a memory request, and should handle requests for zero bytes; class-specific versions should handle requests for larger blocks than expected. operator delete should do nothing if passed a pointer that is null; class specific versions should handle blocks that are larger than expected.
Item-50 Understand when it makes sense to replace new and delete
· β 5 min read
There are many valid reasons for writing custom versions of new and delete, including improving performance, debugging heap usage errors, and collecting heap usage information.
