From: Beman Dawes (beman_at_[hidden])
Date: 1999-11-29 09:43:30
There are two ways to provide call_traits:
* A call_traits template which does nothing else. To use, write
"call_traits<T>::type". Advantage: simple and to-the-point. But if
traits classes proliferate, doing separate specializations for user
defined types becomes painful.
* As part of a more general type_traits template. To use, write
"type_traits<T>::call_type". Advantage: centralizes traits issues.
But as Darin Adler pointed out, could be come a "slippery slope"
leading to all sorts of marginally useful garbage.
My gut feeling is to stick with a separate call_traits template. But
if anyone thinks otherwise, now would be a good time to speak up.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk