A Collection of Intrusive Containters.

Files
file	DListIn.h
	Intrusive Double Linked List.
file	DListIn.hpp
	Intrusive Double Linked List, Implementation.
file	ListIn.h
	Intrusive Singly Linked List.
file	ListIn.hpp
	Intrusive Singly Linked List, Implementation.
file	TreeIn.h
	Intrusive Binary Tree (unbalenced).
file	TreeIn.hpp
	Intrusive Binary Tree (unbalenced), Implementation.

Classes
class	DListInRoot< R, N, n >
class	DListInNode< R, N, n >
class	ListInRoot< R, N, n >
class	ListInNode< R, N, n >
class	TreeInRoot< R, N, K, n >
class	TreeInNode< R, N, K, n >

Detailed Description

The Intrusive Container Collection provides a set of containers that provide 1:many mappings from a "Containing" class to a "Node" class. This library assumes that the classes are "Identity" based (as opposed to "Value" based). It also provides a bi-directional mapping where the Node know what container it is in.

To use this library the Contianing class (called the Root) and the Node class must each derive from a class templates like xxxRoot<> and xxxNode<> repectfully (xxx will be replaced with the name of the container type). The templates will have two or three parameters. The first is the type of the Root class, the second is the type of the Node class, and the third is an optional number to allow a given Root-Node pair to have multiple relations of the same type, and have unique base types to perform these actions.

• The types will need to be declared before use, so typically there will need to be a forward decleration for the types.
• The types will generally be defined before any of the member functions in the container templates are used.
• The derivation of the container base class should be public, or at least the xxxRoot and xxxNode classes both made friends as they need to be able to convert pointer types.
• The operation functions in the container classes are declared protected, if the Root/Node class wishes to make some operation public, it should provide a "thunking" function to provide the access.
• If a class derives from mutiple containers, it may need to use scope resolution operators to select the right sub class to avoid ambiguity errors.