Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Tue, 30 Apr 2002 14:05:16 +0200 From: Pavel Tsekov Reply-To: Pavel Tsekov Organization: Syntrex, Inc. X-Priority: 3 (Normal) Message-ID: <18114622075.20020430140516@syntrex.com> To: "Robert Collins" CC: "CygWin Apps" Subject: Re: setup.exe exception handling guidelines In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Robert, Tuesday, April 30, 2002, 1:09:48 PM, you wrote: [snip] RC> Exceptions that can be thrown: RC> I'm going to create a base Exception class, from which all thrown RC> exceptions should derive. No char/string or String exceptions are RC> allowed. This allows a generic catch-all Exception handler, and by RC> subclassing, more specific handlers can sit in front of it. What about the standard C++ library exception class ? In the recent threads regarding setup and libgetopt++ I red that we libstdc++ can be used now ?