X-Spam-Check-By: sourceware.org Message-ID: <4419CCCD.EF1204C7@dessent.net> Date: Thu, 16 Mar 2006 12:38:37 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin list Subject: Re: Bug in dlopen() (or following) code in Cygwin1.dll v 1.5.19-4 References: <031620061941 DOT 903 DOT 4419BF5E000BEFE80000038722007456720A050E040D0C079D0A AT comcast DOT net> <4419CB81 DOT 8090200 AT huarp DOT harvard DOT edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Norton Allen wrote: > > So maybe it looks weird. C++ is like that! > > I would argue that this isn't a feature of C++ in that it cannot be > implemented within the language but must use assembler for a > specific architecture, but I agree that the paradigm of not needing > to check every case is very cool. It uses the automatic destructor mechanism of C++ to cleanly remove the SEH fault handler whenever the variable goes out of scope. So in a sense that is C++ magic, but the actual fault-trapping capability is provided by SEH which is a service provided by windows and is language-agnostic. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/