[prev] [thread] [next] [lurker] [Date index for 2007/01/30]
> On Mon, 29 Jan 2007, Peter da Silva wrote: > > On Jan 29, 2007, at 4:27 PM, Phil!Gregory wrote: > > > try / finally. > > Unless there's some magic involved, you still have to keep track of where you > > are in the try block so you can unwind things properly. > The C++ answer is to use objects for resource allocation and reclamation, > so that when an exception is thrown the destructors are called as the > stack is unwound and things are automatically tidied up. So you create objects representing external resources like files, database tables, locks, and never expose an uncommitted transaction in any other way?
Generated at 23:01 on 06 Feb 2007 by mariachi 0.52