scope_guard VS human-asmjs

E.g. see this implementation: https://ricab.github.io/scope_guard/

But also I should make the point that you generally don't need to write defer-like statements at all when using RAII because it's implemented in the actual type. So it's only more code overall for types that are used only once or maybe twice.

Meanwhile I will check and use https://github.com/ricab/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/memory corruption.

Again, Scope Exit Guards solve your problem!

One of my colleagues told me to stop doing that because in (I think) V8 these values are immediately converted back to a double nowadays. So annotating all code with |0 doesn't really add speed benefits there, just extra conversions between doubles and integers. Said colleague used to maintain human-asmjs so I trust he knows what he's talking about.

[0] https://github.com/zbjornson/human-asmjs