Message du 21/03/11 16:32 De : "Jeffrey Lee Hellrung, Jr." Robert Stewart brought up a good point on the redundancy of the "_type" suffix, so although the above alternatives to your current metafunction names are longer, that will be mostly mitigated by removing the redundant "_type" suffix. However, we do have free function analogues of these metafunctions, correct? Maybe you can put the metafunctions in a result_of namespace, as Boost.Fusion does?
[I'm hoping the angle brackets get preserved...]
Me too. Lately I was using the Nabble web interface. I have no had any problems in the past, but it seems not be the case now.
namespace result_of{ template< class E > struct native_enum; template< class E > struct underlying_integer; template< class E > struct scoped_enum; } // namespace result_of template< class E > typename result_of::native_enum::type native_enum(const E e); // etc.
I like the result_of trick. What I don't like too much is underlying_integer :( Best, Vicente