Re: template specialization

From:

Abhishek Padmanabh <abhishek.padmanabh@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Sat, 13 Sep 2008 09:43:15 -0700 (PDT)

Message-ID:

<f40d9d8e-13c6-4f7f-9330-8dc13bed9285@s28g2000prd.googlegroups.com>

On Sep 13, 5:51 pm, Konstantin <klk...@panix.com> wrote:

I have two possible implementations of my class:

template <typename T>
class MyContainer
{
public:
    typedef typename std::set<T>::const_iterator const_iterator;
    void add( T id ) { data.insert(id); }
    void remove( T id ) { data.erase(id); }
private:
    std::set<T> data;

};

template <typename T>
class MyContainer
{
public:
    typedef typename std::list<T>::const_iterator const_iterator;
    void add( T id ) { data.push_back(id); }
    void remove( T id ) { data.remove(id); }
private:
    std::list<T> data;

};

which suggests that another parameter in the template could be added.

How to specialize the template correctly so that I could, for example, sw=

itch the underlying container:

It's not clear what your problem is. If you want to write container
adaptors, try looking at some examples of those in the standard
library for example, std::priority_queue<>. You would need an extra
template parameter for the container to choose as you rightly
observerd. But I am not sure what specialization you are asking of?
Are you saying your template should be instantiable only on std::set
and std::list?

typedef MyContainer<InstanceID, set>::const_iterator mycontainer_iterator=

;

MyContainer<InstanceID, set> mycontainer;

or

typedef MyContainer<InstanceID, list>::const_iterator mycontainer_iterato=

MyContainer<InstanceID, list> mycontainer;