Aaron W. LaFramboise wrote:
Jonathan Turkanis wrote:
scope_guard is exactly what I was looking for here.
Its too bad, though, that the syntax for it really isn't that great. One thing I don't like to see in a design of a reusable component is something that requires a lot of structure that doesn't have anything to do with the problem domain.
Ideally we would have built-in lamba expressions.
In any case, would it be possible to move scope_guard to a place where users may legitimately use it, rather than detail? Is there a particular reason that arbitrary code shouldn't use it, or that its interface may change in the future, any more than any other documented Boost interface?
After it's moved into detail, there will have to be a fast track review before it is an official library.
I don't see why you need boost::function
<snip>
scope_guard pretty much reimplements what boost::function provides by itself.
Boost.Function adds an extra level of indirection and possibly a dynamic allocation that isn't needed here.
Aaron W. LaFramboise
Jonathan