1 files changed, 39 insertions, 0 deletions
diff --git a/doc/aapl/ex_avlimel.cpp b/doc/aapl/ex_avlimel.cpp
new file mode 100644
index 00000000..2fadaa3f
--- /dev/null
+++ b/doc/aapl/ex_avlimel.cpp
@@ -0,0 +1,39 @@
+#include "avlimel.h"
+
+/* Forward the element struct so we can pass it to AvlTreeEl. */
+struct CustomEl;
+
+/* Make two base structures that will be used by 
+ * the tree to resolve ambiguites. */
+struct CustomElBase1 : public AvliTreeEl<CustomEl> {};
+struct CustomElBase2 : public AvliTreeEl<CustomEl> {};
+
+struct CustomEl :
+        public CustomElBase1,
+        public CustomElBase2,
+        public CmpOrd<int>
+{
+    /* For our purposes. */
+    CustomEl(int key, const char *data) : key(key), data(data) { }
+
+    const int getKey() { return key; }
+    int key;
+    const char *data;
+};
+
+int main()
+{
+    /* Specify to AvliMel which base to use. */
+    AvliMel< CustomEl, int, CustomElBase1 > avltree1;
+    AvliMel< CustomEl, int, CustomElBase2 > avltree2;
+
+    /* With AvliMel it makes the most sense to new the element ourseves
+     * rather than letting the tree do it for use. */
+    CustomEl *avlElement = new CustomEl( 1, "CustomEl" );
+
+    /* These two calls are completely independant and safe. */
+    avltree1.insert( avlElement );
+    avltree2.insert( avlElement );
+
+    return 0;
+}