[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 216
  • Last Modified:

C++ templates

I'm looking for some information or discussion on some of
more odd uses of C++ templates, particularly of the forms

     class A : public B<A>

     template<class B>
     class D : public B

and similar such forms where you are templatizing some
aspect of an inherhitance hierarchy, and introducing what
looks like strange coupling between base and derived
classes.


I've tried, without luck, to find J. Coplien's C++ report
article on Curiously Recurring Template Patterns. I'm
looking for insight on how these constucts are used,
how they are useful, etc.

Hoping there's an expert out there that can enlighten me!

Thanks!

--shri
0
shriv
Asked:
shriv
  • 3
1 Solution
 
yonatCommented:
There was an article by James Coplien in the C++ Report (I think)  a while back about this. The title was something like "Curiously Recurring Template Patterns".

If I remember correctly, class A : public B<A> is used to achieve code reuse without lossing type safety: B implements the algorithms, and some of it's functions return A-s. Using this form, B "knows" the specific A used, so it can return the right type.

Example:

template<class T>
class Singleton
{
public:
   static T& instance();
protected:
   Singleton() {}
private:
   Singleton(const Singleton&);
   Singleton& operator=(const Singleton&);
};

class Database: public Singleton<Database>
{
private:
   Database();
   friend class Singleton<Database>;
};

template<class B> class D : private B can be used to implement the adapter pattern. I am not sure what you can use public derivation for in this case.

Hope this helps.
0
 
yonatCommented:
It was the February 1995 issue, and is reprinted in the book "C++ Gems".
0
 
shrivAuthor Commented:
I appreciate the pointer to the article. I think, though, that the implications of these template
forms are more subtle than the explanation. I understand that templates are used for
type saftey & reuse: this is the most common usage in collection classes. The "deriving
from itself" appears to be something else entirely, and I believe, has uses beyond
just the singleton example, uses which I'm still unable to grok at this point.

I'd also appreciate an expansion on the adapter pattern implementation.


0
 
yonatCommented:
Here is another example of class A : public B<A>: Let's say you want to keep track of all instances of a class. Then you write:

template <typename T>
class TypeTracker
{
        static std::List<TypeTracker *> theListOfAllT;
public:
        TypeTracker()  { theListOfAllT.push_back(this); }
        ~TypeTracker() { theListOfAllT.erase(this); }
        staic const std::List<TypeTracker *> &getAll() { return theListOfAll; }
};
TypeTracker::theListOfAll;

class MyTrackedClass : virtual public TypeTracker<MyTrackedClass>
{
        ...
};

As for the adapter, see more info at http://rampages.onramp.net/~huston/adapter.html and http://rampages.onramp.net/~huston/adapter.cpp .

0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now