From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19735 invoked by alias); 24 Apr 2003 22:26:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 19711 invoked by uid 71); 24 Apr 2003 22:26:00 -0000 Date: Thu, 24 Apr 2003 22:26:00 -0000 Message-ID: <20030424222600.19710.qmail@sources.redhat.com> To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Benjamin Kosnik Subject: Re: libstdc++/10132: filebuf destructor throws exceptions Reply-To: Benjamin Kosnik X-SW-Source: 2003-04/txt/msg01058.txt.bz2 List-Id: The following reply was made to PR libstdc++/10132; it has been noted by GNATS. From: Benjamin Kosnik To: =?ISO-8859-1?Q?P=E9tur_Run=F3lfsson?= Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/10132: filebuf destructor throws exceptions Date: Thu, 24 Apr 2003 17:23:48 -0500 Actually, principle of least surprise/simplicity probably rules here. I suppose the library streambufs should not get in the way of possible exceptions, should prevent resource leaks and should instead let io bits or user try/catch deal with this. Let me implement 3, and come up with a filebuf::_M_close throw(). -benjamin