id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
6912	[Phoenix V2] Add tr1_result_of specialization	Michel Morin	Joel de Guzman	"To make `result_of` and `tr1_result_of` equivalent, we have to add specialization of `tr1_result_of`. 
(Boost.Phoenix V2 already has specialization of `result_of`.)

Also, it would be nice to avoid specialization of `result_of`, when we use decltype-based `result_of`. 
(As for `tr1_result_of`, it should be specialized even when decltype-based `result_of` is used.)

So, instead of 
{{{
template <...>
struct result_of<F()>
{
    typedef XXXX type;
};
}}}
we should write
{{{
#if !defined(BOOST_RESULT_OF_USE_DECLTYPE) || defined(BOOST_NO_DECLTYPE)
template <...>
struct result_of<F()>
{
    typedef XXXX type;
};
#endif

template <...>
struct tr1_result_of<F()>
{
    typedef XXXX type;
};
}}}

A quick grep said the following file specializes `result_of`.
* spirit/home/phoenix/core/actor.hpp

Here is a related ticket of Boost.Phoenix V3: #6911"	Bugs	closed	To Be Determined	spirit	Boost Development Trunk	Problem	fixed