What do you use RAII for?

[dean]

Hi,

What kinds of things have you used Resource Acquisition is
Initialization for? I've been using it in a few places and its
remarkably useful. Here is where I've use this currently:

1. Creating and/or maintaining hourglass cursors in and between
function calls.
2. Oracle transaction handling and rolling back on exception.
3. Setting bind variable lifetimes in an SQL library.
4. Opening and closing files.
5. Opening and closing database cursors.

Thanks for useful tips!

-Dean

 

[Paul Brettschneider]

Hi,

What kinds of things have you used Resource Acquisition is
Initialization for? I've been using it in a few places and its
remarkably useful. Here is where I've use this currently:

1. Creating and/or maintaining hourglass cursors in and between
function calls.
2. Oracle transaction handling and rolling back on exception.
3. Setting bind variable lifetimes in an SQL library.
4. Opening and closing files.
5. Opening and closing database cursors.

* mutexes/rwlocks

 

[Yannick Tremblay]

Hi,

What kinds of things have you used Resource Acquisition is
Initialization for? I've been using it in a few places and its
remarkably useful. Here is where I've use this currently:

1. Creating and/or maintaining hourglass cursors in and between
function calls.
2. Oracle transaction handling and rolling back on exception.
3. Setting bind variable lifetimes in an SQL library.
4. Opening and closing files.
5. Opening and closing database cursors.

Thanks for useful tips!

Everything (well almost).

RAII is one of the most important idiom in C++ and the great thing is
that it is incredibly versatile. Are you using standard containers?
Then you are using RAII.

Yan

 

[Michael Oswald]

1. Creating and/or maintaining hourglass cursors in and between
function calls.
2. Oracle transaction handling and rolling back on exception.
3. Setting bind variable lifetimes in an SQL library.
4. Opening and closing files.
5. Opening and closing database cursors.

6. Debug-Logging entering and leaving of a function

lg,
Michael

 

[James Kanze]

What kinds of things have you used Resource Acquisition is
Initialization for? I've been using it in a few places and its
remarkably useful. Here is where I've use this currently:

1. Creating and/or maintaining hourglass cursors in and between
function calls.
2. Oracle transaction handling and rolling back on exception.
3. Setting bind variable lifetimes in an SQL library.
4. Opening and closing files.
5. Opening and closing database cursors.

It depends on just how far you're willing to stretch it. I
frequently use something more or less similar for transaction
management; if the destructor is called before the commit
function has been called, it does a rollback. I guess the
presence of the commit function means that it isn't strictly
speaking RAII, but in practice, while I often need scoped clean
up, except for resources like locks, the clean-up in the case of
errors is almost always different from the normal case. If
you're outputting to a file, for example, you'll remove the file
if it hasn't been correctly closed (committed), or if there was
an error on the close.

 

[Erik Wikström]

Hi,

What kinds of things have you used Resource Acquisition is
Initialization for? I've been using it in a few places and its
remarkably useful. Here is where I've use this currently:

1. Creating and/or maintaining hourglass cursors in and between
function calls.
2. Oracle transaction handling and rolling back on exception.
3. Setting bind variable lifetimes in an SQL library.
4. Opening and closing files.
5. Opening and closing database cursors.

Memory and file stream management mostly.

 

[Jon Harrop]

What kinds of things have you used Resource Acquisition is
Initialization for?

RAII is incredibly useful because it handles a tiny number of the use cases
of higher-order functions. In the absence of first-class functions, RAII is
really your only choice.

 

[Roland Pibinger]

What kinds of things have you used Resource Acquisition is
Initialization for? I've been using it in a few places and its
remarkably useful. Here is where I've use this currently:

4. Opening and closing files.

Closing files in the destructor is only correct for files that have
been opened 'read only'. After writing to a file you need to respond
to an error from (f)close (unless the file contents is dispensable).
But it's too late to attempt error reporting in the destructor
(throwing exceptions from destructors is not an option in C++).