Ok Thanks. I was looking at the specializations and didn't even see the enable parameters. ----- Original Message -----
From: Thomas Heller
To: boost-users@lists.boost.org Cc: Sent: Saturday, February 25, 2012 7:43 AM Subject: Re: [Boost-users] [phoenix] Extending actors On 02/24/2012 06:11 PM, paul Fultz wrote:
Thanks so much for the help. A couple more questions:
1) Is it possible to add an enable parameter to is_actor in futureversions of phoenix?
is_actor is defined as:
namespace boost { namespace phoenix { /////////////////////////////////////////////////////////////////////////////// // // is_actor<T> // // Tests if T is an actor. Evaluates to mpl::true_ or mpl::false_ // ///////////////////////////////////////////////////////////////////////////////
template
struct is_actor : mpl::false_ {}; }} 2) Is the is_actor trait used internally by phoenix? The reason I ask is I am thinking about using my own is_actor trait for my extended actors unitl maybe this gets updated in boost.
At the moment it is not really used internally by phoenix. But it is used by, for example spirit. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users