Hi, I think whether or not there was a reason to not do it in the first place, the idea should be revisited. I recently implemented a bit of code that figured out the minimum number of parameters that would be required for an arbitrary bind expression. After a while, there was a boatload of code that was just to do with getting around the current bind implementation's decisions that I decided not to pursue it any further - the thing I really wanted to do was do a fusion::for_each... But that was not to be for me! -----Original Message----- From: boost-users-bounces@lists.boost.org on behalf of Gottlob Frege Sent: Wed 3/21/2007 7:11 PM To: boost-users@lists.boost.org Subject: [Boost-users] bind doesn't use tuple why doesn't bind use tuple (internally)? I'm tempted to leave the email as just that. No more to say. OK, maybe one thing - I'm not asking because I necessarily think it should, I can imagine there are reasons, just wondering what they might be.