From: Bruno Lalande [mailto:bruno.lalande@gmail.com] Wouldn't the following give the desired result?
Yes, in fact after I found no answers in my mailbox this morning I
noodled on the problem some more and came up with that solution. The
difficulty is that there is a lot of non-variadic cruft common to the
general and specialized template classes. I didn't want to repeat all of
that.
My solution was to insert a new intermediate template class in the
hierarchy. But that would scale poorly if there were a richer set of
variadic member enabling conditions. And maintaining extra layers of
forwarding constructor definitions can be tedious and error-prone. Oh
well, one can't have everything.
To summarize the issue: boost::enable_if does not seem to work for
selectively declaring member function signatures so if you have members
with signatures that vary in a complex way depending on template
parameters you have to use class template specialization. To avoid
repeating non-variadic member declarations, factor them into a common
public base class.
Here's my class hierarchy now:
template