Re: [ADVANCED-DOTNET] Exception safety and IDispose in C++

2002-10-11 Thread Keith Hill
On Thu, 10 Oct 2002 13:11:20 -0500, Trey Nash <[EMAIL PROTECTED]> wrote: >I'm glad that I, at least, found some validation of my concerns regarding >these issues. It's clear that there needs to be the deterministic >destruction idiom available for use as well. And, IMHO, the dispose >pattern is

Re: [ADVANCED-DOTNET] Exception safety and IDispose in C++

2002-10-11 Thread Christoph Nahr
At 09:42 10.10.2002 -0600, you wrote: >You never used or CFile? Granted, the __finally blocks are a >nice addition, but they are a poor replacement for an object that cleans >itself up correctly and deterministically. Objects rarely need to clean up after themselves in a deterministic fashion w

Re: [ADVANCED-DOTNET] Exception safety and IDispose in C++

2002-10-11 Thread Christoph Nahr
Trey, Sorry for my extended rants, looks like I misunderstood your posts -- there are many misconceptions about the role of C# destructors / finalizers and IDispose floating about, so that's what I was trying to clear up. But since you already know what you're doing I'm afraid I can't offer much

Re: [ADVANCED-DOTNET] Exception safety and IDispose in C++

2002-10-10 Thread Trey Nash
> Optimally, you would like to have commit/rollback behavior in the face > of exceptions. The .NET garbage collector provides little support for > this type of exception safety. > > See basic and strong exception guarantees. > http://www.boost.org/more/generic_exception_safety.html This is EXACTL

Re: [ADVANCED-DOTNET] Exception safety and IDispose in C++

2002-10-10 Thread Johan Ericsson
>>Moreover, who else agrees that __finally blocks are ugly and extremely >>error prone and difficult to maintain? What sort of solution could we use >>to allow what C++ developers know as a destructor to do automatic cleanup? >I don't agree, I love them! Much better than writing those stupid C++

Re: [ADVANCED-DOTNET] Exception safety and IDispose in C++

2002-10-10 Thread Trey Nash
> I suspect you're stuck in a C++ paradigm where you feel you have to > design objects that automatically eradicate themselves as soon as they > get out of scope. That's absolutely not the .NET paradigm. The finally I'm groking all that just fine. I have read the Richter book that you mention an

Re: [ADVANCED-DOTNET] Exception safety and IDispose in C++

2002-10-10 Thread Christoph Nahr
At 15:56 09.10.2002 -0500, you wrote: >Hi all, > >I originally posted this to DOTNET-CLR and meant to voice the same ideas >here. I hope this issue is not an old one, but here goes. > >Up front, I was wondering if the C++ managed extensions package provides >anything such as the C# 'using' statem

[ADVANCED-DOTNET] Exception safety and IDispose in C++

2002-10-09 Thread Trey Nash
Hi all, I originally posted this to DOTNET-CLR and meant to voice the same ideas here. I hope this issue is not an old one, but here goes. Up front, I was wondering if the C++ managed extensions package provides anything such as the C# 'using' statement to make use of the IDispose easier. Some