[signals2] lamda placeholder collision

I am converting some older code to use signals2. The old source uses boost.lambda which results in a collision of placeholders from bind (included by signals2) and lambda. I converted to phoenix about a year ago and I'll fix this "problem" by moving the lambdas to phoenix ... but ... what is supposed to be the correct course of action for source wanting to use both signals2 and Boost.Lambda? Regards - michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 10 March 2010, Michael Caisse wrote:
This isn't a signals2 specific issue is it? It's more a boost::bind versus lambda thing. Anyways, the lambda placeholders are in their own namespace, so if you get rid of "using namespace boost::lambda" from your code and qualify the uses of the lambda placeholders you should be okay, right? I should say though I've never actually tried combining boost::bind and lambda myself. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkuXqPMACgkQ5vihyNWuA4UAeQCdHBVZsNLFW9MmTQ+bxk9726Fb yIUAoIALcBIixUnhHn7IVC70zcD/88sS =+2yK -----END PGP SIGNATURE-----
participants (2)
-
Frank Mori Hess
-
Michael Caisse