Forbidding template instantiation for specific type

[Marcin Kalicinski]

Hi,

I am modernizing a small library that is being currently in use by some
people. In the new version I want to forbid use of a template function with
argument of const char * (i.e. I want to get compile errors when it
happens). For the rest of the types function should work ok.

// A template function, in old version of the library allowed for all types
template<typename T> void func(T t)
{
/* ... */
}

Now I want to forbid its use with const char *. For example I could use
specialization in the following way:

template<> void func(const char *)
{
const int a = 0;
a = 1;
}

Is there a cleaner way of achieving the same? Expecially to get better error
message? (ideally the error message should say that func(const char*) is
undefined).

Best regards,
Marcin

[Buster]

Marcin Kalicinski wrote:

Hi,

I am modernizing a small library that is being currently in use by some
people. In the new version I want to forbid use of a template function with
argument of const char * (i.e. I want to get compile errors when it
happens). For the rest of the types function should work ok.

// A template function, in old version of the library allowed for all types
template<typename T> void func(T t)
{
/* ... */
}

Now I want to forbid its use with const char *. For example I could use
specialization in the following way:

template<> void func(const char *)
{
const int a = 0;
a = 1;
}

Is there a cleaner way of achieving the same? Expecially to get better error
message? (ideally the error message should say that func(const char*) is
undefined).

Error messages vary across implementations, but you can try

template <> void func (const char *)
{
int constraints_func_undefined_for_pointer_to_const_ch ar [-1];
}

Regards,
Buster.

[Buster]

Marcin Kalicinski wrote:

Hi,

I am modernizing a small library that is being currently in use by some
people. In the new version I want to forbid use of a template function with
argument of const char * (i.e. I want to get compile errors when it
happens). For the rest of the types function should work ok.

// A template function, in old version of the library allowed for all types
template<typename T> void func(T t)
{
/* ... */
}

Now I want to forbid its use with const char *. For example I could use
specialization in the following way:

template<> void func(const char *)
{
const int a = 0;
a = 1;
}

Is there a cleaner way of achieving the same? Expecially to get better error
message? (ideally the error message should say that func(const char*) is
undefined).

Oh man. That's too funny. Ignore my other post. Just don't define it!

template <> void func (const char *);

You'll get a link error.

Regards,
Buster.

[Marcin Kalicinski]

Uzytkownik "Buster" <no***@nowhere.com> napisal w wiadomosci
news:c4**********@newsg3.svr.pol.co.uk...

Marcin Kalicinski wrote:

Hi,

I am modernizing a small library that is being currently in use by some
people. In the new version I want to forbid use of a template function with argument of const char * (i.e. I want to get compile errors when it
happens). For the rest of the types function should work ok.

// A template function, in old version of the library allowed for all types template<typename T> void func(T t)
{
/* ... */
}

Now I want to forbid its use with const char *. For example I could use
specialization in the following way:

template<> void func(const char *)
{
const int a = 0;
a = 1;
}

Is there a cleaner way of achieving the same? Expecially to get better error message? (ideally the error message should say that func(const char*) is
undefined).

Oh man. That's too funny. Ignore my other post. Just don't define it!

template <> void func (const char *);

You'll get a link error.

Now that's a clever idea. Thanks!

Best regards,
Marcin

[Dan Moos]

Oh man. That's too funny. Ignore my other post. Just don't define it!

template <> void func (const char *);

You'll get a link error.

Now that's a clever idea. Thanks!

Best regards,

I guess I don't see how that is an improvement over the OP's initial method.
Both will confuse an unsuspecting user of the template who isn't "In the
know". I other words, if I try to use that template with a const char *,
and I get a link error, I'm gonna be one confused dude, and can't imagine
coming to the conclusion that it is intended behaviour! I actually liked the
first idea of creating an array with an informative name, and giving it a
negative number as a size. I actually found that to be pretty clever! The
trick is giving the array a name that makes the situation obvious, like
"USER_this_template_does_not_work_with_const_char_ pointers"

[Buster]

Dan Moos wrote:

Oh man. That's too funny. Ignore my other post. Just don't define it!

template <> void func (const char *);

You'll get a link error.

Now that's a clever idea. Thanks!

Best regards,

I guess I don't see how that is an improvement over the OP's initial method.
Both will confuse an unsuspecting user of the template who isn't "In the
know". I other words, if I try to use that template with a const char *,
and I get a link error, I'm gonna be one confused dude, and can't imagine
coming to the conclusion that it is intended behaviour! I actually liked the
first idea of creating an array with an informative name, and giving it a
negative number as a size. I actually found that to be pretty clever! The
trick is giving the array a name that makes the situation obvious, like
"USER_this_template_does_not_work_with_const_char_ pointers"

Good point. We should use plain English. I was about to suggest
'function_func_is_not_implemented_for_arguments_of _type_pointer_to_const_char'
before I thought of the other idea. But the OP did ask for an error
saying that the function was undefined.