On Fri, Apr 2, 2010 at 9:32 PM, OvermindDL1 <overminddl1@gmail.com> wrote:
On Thu, Apr 1, 2010 at 2:38 PM, Daniel Walker <daniel.j.walker@gmail.com> wrote:
This patch seemed to be missing, so I re-uploaded it. The patch was the result of (no pun intended) some discussion. I found an e-mail with an overview here http://tinyurl.com/2jgtld. To my knowledge, the patch was never applied. It's been a few years, but my recollection is that a rewrite of lambda was anticipated, which would address these issues, and there was little demand for result_of/lambda compatibility in the meantime. Also, there was no active maintainer for the lambda library.
Actually, Boost.Phoenix I think is what will completely replace Lambda, have you tried using it, does it have that same problem?
Phoenix may be used in some eventual rewrite, but that's not the immediate issue. By the way, boost::result_of does work with lambda functors when decltype is available. So, going forward, this will only be an issue on legacy compilers that lack decltype. ~Daniel