scope_guard

> low level details leak into your high level description of code, making the two coupled. You can’t make them invisible. It's your job to make it not to leak. You have to write Modern C++ wrappers around C libs. Similarity, The same can be said for Java. You can do low level in Java. C++ is not C. C++ has backward compatibility with C. Look at Boost folks, they wrote a Modern C++ wrapper around a C HTTP parser. > And as I said, I’m familiar with RAII, it’s really great when the given object is scope-based, but can’t do anything otherwise. Nothing is impossible. You can use Scope Exit Guard with QT Widget. https://github.com/ricab/scope_guard > And if the new subclass has some non-standard object life cycle you HAVE to handle that case somewhere else, modifying another aspect of the code. It is not invisible, unless you want leaking code

This seems like a great place to plug C++ - Destructors are what you want. While I'm personally a fan of C++-as-a-whole, there's nothing stopping you using C-with-classes. You can "emulate" the defer statement with a Scope Guard[0], or if you're willing to use a macro, you can use the __COUNTER__ macro as an "anonymous" variable. [0] https://github.com/ricab/scope_guard