On 9/2/12 7:24 AM, Eric Niebler wrote:
On 9/1/2012 1:39 PM, Daniel Walker wrote:
Eric, I'm comfortable with the state of result_of on trunk, if you want to sync it with release. I suppose now is as good a time as any, but I'll trust your judgement on the timing.
Thanks, Daniel. I thought about it some and decided to merge the change to release, even though it breaks Phoenix on modern compilers. I decided that ultimately, it was more important that boost::result_of work with C++11 lambdas. We can't bugs in 1 or 2 libraries hold up progress for everybody.
We will have to make a very BOLD announcement in the release notes of 1.52. Not only will users of Phoenix be affected; anybody who relies on boost::result_of to use the TR1 protocol will be broken by this. This might be a painful transition for some, but there's no helping that.
I have no problem with this as long as there's clear documentation on what users would expect and how to deal with them in their code.
I also hope that we won't have to ship a broken Phoenix in 1.52 -- that the Phoenix maintainers will step up and fix it. Joel, Thomas?
Sure, let's do it. Thomas? Regards, -- Joel de Guzman http://www.boostpro.com http://boost-spirit.com