Computers

Covers the design of a global memory manager that is as fast and space-efficient as per-class allocators.

Delves deeper into the question of what operator new() failures mean, and how best to detect and handle them.

Explains why a class that provides its own class-specific operator new(), or operator new[](), should also provide corresponding class-specific versions of plain new, in-place new, and nothrow new.

Answers the question of how much memory the various standard containers use to store the same number of objects of the same type T.

Explains why auto_ptr neatly solves common C++ design and coding problems, and why using it can lead to more robust code.

Explains what smart pointers are, why they should be used, and which one should be used.

This article explains design principles that will help keeping memory management error out of C++ code.

Matthew and Bjorn update the well-known Rule of The Big Three, explaining which one of those member functions is not always needed.

This article provides an in-depth look at the "pure virtual function called" error message.

Presents a list of simple, powerful techniques that can be used to deal with memory in C++ programs.

This article discusses C++ in the context of several other popular languages. It also describes the kinds of memory errors that can occur in C++ programs.

This article follows through the implementation of a smart pointer class that overcames deficiencies of existing smart pointer implementations.

Memory management is scary. It should be: A lot can go wrong--often very wrong. But a moderately experienced C or C++ programmer can learn and understand memory hazards completely.

Andrei Alexandrescu discusses smart pointers, from their simplest aspects to their most complex ones and from the most obvious errors in implementing them to the subtlest ones--some of which also happen to be the most gruesome.

Stephen Dewhurst discusses how the various features of C++ are used together in memory management, how they sometimes interact in surprising ways, and how to simplify their interactions.

Andrei Alexandrescu navigates through the sometimes treacherous waters of using smart pointers, which imitate built-in pointers in syntax and semantics but perform a host of additional tasks that built-in pointers can't.

This article deals with refactoring the code originally presented in part 1 in order to allow polymorphic types to be used.

An article on using garbage collection through the use of smart pointers.

Introduces two key concepts: the use of a generic requirements based approach to simplify and adapt the use of the counted body pattern and the ability to dynamically and non-intrusively add capabilities to fixed types using the runtime mixin pattern.

Introduces smart pointers and takes a look at Boosts various smart pointer templates (scoped_ptr, scoped_array, shared_ptr, and shared_array).

Show how garbage collection works and what it actually costs.