C++
- Getting started with C++
- Awesome Book
- Awesome Community
- Awesome Course
- Awesome Tutorial
- Awesome YouTube
- Alignment
- Argument Dependent Name Lookup
- Arithmitic Metaprogramming
- Arrays
- Atomic Types
- Attributes
- auto
- Basic input/output in c++
- Basic Type Keywords
- Bit fields
- Bit Manipulation
- Bit Operators
- Build Systems
- C incompatibilities
- C++ Containers
- C++ Debugging and Debug-prevention Tools & Techniques
- C++ function "call by value" vs. "call by reference"
- C++ Streams
- C++11 Memory Model
- Callable Objects
- Classes/Structures
- Client server examples
- Common compile/linker errors (GCC)
- Compiling and Building
- Concurrency With OpenMP
- Const Correctness
- const keyword
- Constant class member functions
- constexpr
- Copy Elision
- Copying vs Assignment
- Curiously Recurring Template Pattern (CRTP)
- Data Structures in C++
-
Date and time using
header - decltype
- Design pattern implementation in C++
- Digit separators
- Enumeration
- Exceptions
- Explicit type conversions
- Expression templates
- File I/O
- Floating Point Arithmetic
- Flow Control
- Fold Expressions
- Friend keyword
- Function Overloading
- Function Template Overloading
- Futures and Promises
- Header Files
- Implementation-defined behavior
- Inline functions
- Inline variables
- Internationalization in C++
- Iteration
- Iterators
- Keywords
- Lambdas
- Layout of object types
- Linkage specifications
- Literals
- Loops
- Memory management
- Metaprogramming
- More undefined behaviors in C++
- Move Semantics
- mutable keyword
- Mutexes
- Namespaces
- Non-Static Member Functions
- One Definition Rule (ODR)
- Operator Overloading
- operator precedence
- Optimization
- Optimization in C++
- Overload resolution
- Parameter packs
- Perfect Forwarding
- Pimpl Idiom
- Pointers
- Pointers to members
- Polymorphism
- Preprocessor
- Profiling
- RAII: Resource Acquisition Is Initialization
- Random number generation
- Recursion in C++
- Recursive Mutex
- Refactoring Techniques
- References
- Regular expressions
- Resource Management
- Return Type Covariance
- Returning several values from a function
- RTTI: Run-Time Type Information
- Scopes
- Semaphore
- SFINAE (Substitution Failure Is Not An Error)
- Side by Side Comparisons of classic C++ examples solved via C++ vs C++11 vs C++14 vs C++17
- Singleton Design Pattern
- Smart Pointers
- Casting std::shared_ptr pointers
- Getting a shared_ptr referring to this
- Sharing ownership (std::shared_ptr)
- Sharing with temporary ownership (std::weak_ptr)
- Unique ownership (std::unique_ptr)
- Unique ownership without move semantics (auto_ptr)
- Using custom deleters to create a wrapper to a C interface
- Writing a smart pointer: value_ptr
- Sorting
- Special Member Functions
- Standard Library Algorithms
- static_assert
- std::any
- std::array
- std::atomics
- std::forward_list
- std::function: To wrap any element that is callable
- std::integer_sequence
- std::iomanip
- std::map
- std::optional
- std::pair
- std::set and std::multiset
- std::string
- std::variant
- std::vector
- Storage class specifiers
- Stream manipulators
- Templates
- The ISO C++ Standard
- The Rule of Three, Five, And Zero
- The This Pointer
- Thread synchronization structures
- Threading
- Trailing return type
- type deduction
- Type Erasure
- Type Inference
- Type Keywords
- Type Traits
- Typedef and type aliases
- Undefined Behavior
- Unions
- Unit Testing in C++
- Unnamed types
- Unspecified behavior
- User-Defined Literals
- Using declaration
- Using std::unordered_map
- Value and Reference Semantics
- Value Categories
- Variable Declaration Keywords
- Virtual Member Functions
C++ Smart Pointers
Syntax#
std::shared_ptr<ClassType> variableName = std::make_shared<ClassType>(arg1, arg2, ...);std::shared_ptr<ClassType> variableName (new ClassType(arg1, arg2, ...));std::unique_ptr<ClassType> variableName = std::make_unique<ClassType>(arg1, arg2, ...);// C++14std::unique_ptr<ClassType> variableName (new ClassType(arg1, arg2, ...));
Remarks#
C++ is not a memory-managed language. Dynamically allocated memory (i.e. objects created with new) will be "leaked" if it is not explicitly deallocated (with delete). It is the programmer's responsibility to ensure that the dynamically allocated memory is freed before discarding the last pointer to that object.
Smart pointers can be used to automatically manage the scope of dynamically allocated memory (i.e. when the last pointer reference goes out of scope it is deleted).
Smart pointers are preferred over "raw" pointers in most cases. They make the ownership semantics of dynamically allocated memory explicit, by communicating in their names whether an object is intended to be shared or uniquely owned.
Use #include <memory> to be able to use smart pointers.
Smart Pointers Related Examples#
- Casting std::shared_ptr pointers
- Getting a shared_ptr referring to this
- Sharing ownership (std::shared_ptr)
- Sharing with temporary ownership (std::weak_ptr)
- Unique ownership (std::unique_ptr)
- Unique ownership without move semantics (auto_ptr)
- Using custom deleters to create a wrapper to a C interface
- Writing a smart pointer: value_ptr
