On Fri, Oct 7, 2011 at 9:06 AM, niXman wrote:

Better solution:

http://www.boost.org/doc/libs/1_47_0/libs/function_types/doc/html/boost_func...

Ah, yes, that's the thing I'm looking for! result_type NOT result_of. Thanks for putting me straight. - Rob.

On Fri, Oct 7, 2011 at 8:58 AM, Julien Nitard wrote:

Hello,

...

Doesn't Boost.Function support 'result_of', or am I missing something obvious?

More the opposite, result_of doesn't support boost::function and is quite limited without "recent" compiler features.

...

typedef boost::result_of::type my_return_type;

You may want to use "#define BOOST_RESULT_OF_USE_DECLTYPE" if your compiler is recent enough. Explanations in the docs of result_of. Of course if your compiler is even more recent, it may support * std::result_of.*

Hi Julien - I think I've read the relevant pages already, but it seems to come down to whether the Boost.Function properly publishes its return type. I am a little surprised that it seems not to. Thx, R.

On Fri, Oct 7, 2011 at 3:37 PM, Steven Watanabe wrote:

AMDG

On 10/07/2011 01:09 AM, Robert Jones wrote:

...

Hi Julien - I think I've read the relevant pages already, but it seems to come down to whether the Boost.Function properly publishes its return type. I am a little surprised that it seems not to.

It does. As Michel pointed out, you're not using result_of correctly.

Hi Steven, Julien - Indeed it does, which I didn't understand, but I think I now do. Boost.Function objects publish a 'result' templated nested struct, not a nested type, which it must do since the return type may depend on the invocation arguments, so those arguments must be supplied. Thanks for putting me straight. - Rob.