Alexander, I understand your gripes about the lambda syntax, but to be perfectly frank, I have never used lambda expressions in combination with the scope guard (which is maybe why your arguments have so far been unable to convince me). My clean up actions tend to be trivial function calls or functors that don't require any lambda syntax. Moreover, I am convinced any lambda expression wouldn't get through our code inspection for exactly the reasons you bring up. However, I fear that I will face similar resistance to your syntax. It's hard to argue that a macro with (seemingly) un-typed arguments, a code block between curly braces followed by another macro, look anything like C++ (and arguing its correctness based on a future language standard probably won't do me much good either). I think the scope guard functionality is an essential tool for many programmers so its syntax needs to be accessible to the masses. A quick glimpse through some of the other reviews seems to indicate that I am not the only one with this concern. -Ben This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.