Reputation: 132300
Difference between ScopeGuard11 and Boost.ScopeExit - just backwards compatibility?
I recently watched Andrei Alexandrescu's talk in 'C++ and Beyond 2012' (Systematic Error Handling with C++), in which he discusses his ScopeGuard11 construct, and specifically SCOPE_EXIT (second part of the talk; or just read the code here). At the same time, I'm beginning to look into the Boost library, and have noticed the BOOST_SCOPE_EXIT macro (the Boost.ScopeExit library).
These two seem to be quite different implementation-wise (BOOST_SCOPE_EXIT uses Boost.TypeOf, nothing like that in ScopeGuard11's SCOPE_EXIT); and the Boost macro is concerned with parameter capture etc. which is less of an issue in C++11; but beyond that, they seem to offer essentially the same functionality.
Am I right or am I missing something? Could one say that ScopeGuard11 is a 'cleaner' mechanism with the same functionality of Boost.ScopeGuard but with less backwards compatibility?
Upvotes: 3
Views: 1049
Answers (0)
Related Questions
- Does ScopeGuard use really lead to better code?
- BOOST scoped_lock replacement in C++11
- Difference between boost::scoped_ptr<T> and std::unique_ptr<T>
- boost scoped_lock return behavior
- Will there be standardization of scope guard/scope exit idioms?
- boost scoped_lock vs plain lock/unlock
- What does BOOST_SCOPE_EXIT do behind the scenes?
- What is ScopeGuard in C++?
- Proper use of boost Lockguard - Are these two same
- boost::lock_guard vs boost::mutex::scoped_lock