🚀 go-pugleaf

"Mike Collins" <its@TheBottomOfThePost> wrote:

>Hay all, just a quicky, just wondering if anyone had any thoughts on using 
>try... __finally to ensure that a critical section is always released?

Don't do it.

Make an object that has a destructor. In the destructor, put the code to
release the critical section. Now just put the object on the stack -
when the current scope is exited, the critical section *WILL* be
released.

This is a fundamental idea in C++, known as 'Resource Allocation Is
Initialisation' or RAII. You make sure that any resource that must be
allocated and released is owned by an object that, if it still has it
when it gets to destruct, releases it. std::string works this way.
std::fstream works this way. std::vector works this way.

Using try/__finally is not the C++ way, it's the way of Java and other
languages that can't use deterministic destruction.

Alan Bellingham
-- 
Team Browns
<url:http://www.borland.com/newsgroups/> Borland newsgroup descriptions
<url:http://www.borland.com/newsgroups/netiquette.html>      netiquette