C++ Scandal?!

[Paul Dubuc]

You can catch(...) { cleanup; throw; }

But you must also call cleanup at normal function exit. However...


If I have class Q that requires Q::cleanup(), then all methods that use Q
must call cleanup(). That couples Q's internal state (the fact that it
isn't clean yet) to the control flow of all its methods. That is wasteful.

See also:

http://www.informit.com/guides/content.asp?g=cplusplus&SeqNum=189&rl=1

 

[Phlip]

http://www.informit.com/guides/content.asp?g=cplusplus&SeqNum=189&rl=1

That blog is too gentle on Java.

 

[belvis]

but a try/catch/finally in C++ would be fine

it is good to have more options. we can only emulate try/finally with
RAII. this leads to many boring local classes

Try/finally leads to errors. I'd rather be bored than wrong.

Bob

 

[peter koch]

Diego Martins skrev:

but a try/catch/finally in C++ would be fine

it is good to have more options. we can only emulate try/finally with
RAII. this leads to many boring local classes

I disagree. I have never had a need for finally and fear that it will
create plenty of misuse should it be introduced. Scope_guard is fine on
the rare occasions where you need something more involved.

/Peter