From 952643446241157180 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,2cda86d818184499,start X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 1994-01-26 23:31:57 PST Newsgroups: comp.std.c++ Path: gmd.de!newsserver.jvnc.net!darwin.sura.net!howland.reston.ans.net!usc!yeshua.marcam.com!zip.eecs.umich.edu!oldnews2.cis.umn.edu!mmm.mmm.com!us261419 From: hopps@yellow.mmm.com (Kevin J Hopps) Subject: new Thing() failure in ctor Message-ID: Keywords: exception new delete Sender: us261419@mmm.mmm.com (David P. Erickson) Reply-To: kjhopps@mmm.com Organization: 3M - St. Paul, MN 55144-1000 US Date: Wed, 26 Jan 94 16:09:17 GMT Lines: 18 I am issuing another plea to the committee to address what seems to me to be a major hole in the standard as it has evolved thus far. If this has been addressed already, please forgive my plea, and update my on the decision. To reiterate: consider the following statement. Thing* tp = new Thing; Suppose that the memory for Thing is allocated but the constructor for Thing throws an exception. How is the memory for Thing reclaimed? Please give us ammunition for battle with our compiler providers. My current implementation has a memory leak, which gets serious if sizeof(Thing) is large. -- Kevin J. Hopps e-mail: kjhopps@mmm.com 3M Company phone: (612) 737-3300 3M Center, Bldg. 235-3B-16 fax: (612) 737-2700 St. Paul, MN 55144-1000