CODEWITHSUNDEEP
c++templates
gregseth
gregseth

Reputation: 13408

Force type of C++ template

I've a basic template class, but I'd like to restrain the type of the specialisation to a set of classes or types. e.g.:

template <typename T>
class MyClass
{
.../...
private:
    T* _p;
};

MyClass<std::string> a; // OK
MYCLass<short> b;       // OK
MyClass<double> c;      // not OK

Those are just examples, the allowed types may vary.

Is that even possible? If it is, how to do so?

Thanks.

Upvotes: 13

Views: 10716

Answers (6)

Johannes Schaub - litb
Johannes Schaub - litb

Reputation: 506905

Another version is to leave it undefined for the forbidden types

template<typename T>
struct Allowed; // undefined for bad types!

template<> struct Allowed<std::string> { };
template<> struct Allowed<short> { };

template<typename T>
struct MyClass : private Allowed<T> { 
  // ...
};

MyClass<double> m; // nono

Upvotes: 21

UncleBens
UncleBens

Reputation: 41331

Generally it is unnecessary to restrict which types templates can be instantiated with. Either the template is compilable with the given type (and works OK) or it isn't (and produces a compiler error without any effort on the programmer's part).

If you need to put in restrictions, generally the types have something in common that may be described by some type traits that are already available (standard library, boost::type_traits), or you can create a new type trait for them.

For example, here's a template class that only allows integer types, using std::numeric_limits to check it (if you write your own numeric type, you may specialize that so that it would also work with your new integer type). static_assert is C++0x only, if not available use BOOST_STATIC_ASSERT or some other trick.

#include <limits>
#include <string>

template <class T>
class X
{
    static_assert(std::numeric_limits<T>::is_integer, "X can be only instantiated with integer types");
    //...
};

int main()
{
    X<int> xi;
    X<char> xc;
    //X<double> xd;
    //X<std::string> xs;
}

If you only plan to support a handful of arbitrary types with nothing in common (as is apparent from your hypothetical example), one way is to employ typelists. Again boost might make the task a lot easier, but here's how you might roll your own (this only goes half-way, additional work would be required to make declaring the typelist prettier). 

struct no_type {};

template <class T, class U = no_type>
struct t_list
{
    typedef T head;
    typedef U tail;
};

//trait to check if two types are identical
template <class T, class U>
struct is_same
{
    static const bool value = false;
};

template <class T>
struct is_same<T, T>
{
    static const bool value = true;
};

//compile-time recursion to check if T matches any type in list L
template <class T, class L>
struct in_type_list
{
    static const bool value =
        is_same<T, typename L::head>::value || in_type_list<T, typename L::tail>::value;
};

//terminates recursion
template <class T>
struct in_type_list<T, no_type>
{
    static const bool value = false;
};

template <class T>
class X
{
    typedef t_list<double, t_list<int, t_list<char> > > allowed_types; //double, int, char

    //poor man's static_assert
    typedef int check_type [in_type_list<T, allowed_types>::value ? 1 : -1];
    //...
};

int main()
{
    X<char> xc;
    X<int> xi;
    X<double> xd;
    //X<float> xf;
}

Upvotes: 2

Tom
Tom

Reputation: 45104

Im not sure about this, but you could add another template specialization for double template 

class MyClass
{
.../...
private:
    T* _p;
};

template <double> class MyClass
{};

which would work for your example, but not for the general case.

In general, I would add a compile assert to check for unwanted types.

Hope it helps.

Upvotes: 1

Alexander Gessler
Alexander Gessler

Reputation: 46607

Yust a quick idea, I'm sure there are better approaches:

template <typename T> struct protector {
static const int result = 1;
};

template <> struct protector<double> {
static const int result = -1;
};

template <typename T> 
class MyClass
{
   private:
     char isfine[protector<T>::result];
};

It might be better, however, to put a fat comment over your code to keep users from instantiating with the wrong types :-)

Upvotes: 8

AProgrammer
AProgrammer

Reputation: 52284

There are various tricks allowing to check for some things, depending on what your criteria is for the instantiation be allowed or not. In practice you should use an higher lever library for those like Boost's Concept Check.

Upvotes: 1

Axel Gneiting
Axel Gneiting

Reputation: 5403

Take a look at the Boost Concept Check Library: http://www.boost.org/doc/libs/1_42_0/libs/concept_check/concept_check.htm

Upvotes: 6

Related Questions