Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!att!dptg!pegasus!hansen
From: hansen@pegasus.ATT.COM (Tony L. Hansen)
Newsgroups: comp.std.c++
Subject: set_new_handler() and <new.h> standardization
Summary: it needs to be standardized
Keywords: fancy new() management
Message-ID: <4977@pegasus.ATT.COM>
Date: 17 Aug 90 14:01:14 GMT
Reply-To: hansen@pegasus.ATT.COM (Tony L. Hansen)
Organization: AT&T Bell Labs NJ USA
Lines: 20

One of the "library" issues that Bjarne has shied away from specifying
within the reference part of E&S is that of the contents of <new.h> and the
guaranteed availability of set_new_handler(). Since E&S does NOT deal with
library issues at all, they (perhaps rightly) did not include anything
within it regarding <new.h> or set_new_handler().

Now if you look at page 280 on free store, you WILL see a description of
set_new_handler() WITHIN the commentary. However, this is NOT part of the
reference manual and has no binding on anything or anyone.

I found little else within E&S regarding <new.h> other than a statement
on page 7 requiring its existence.

The exact contents of <new.h> need to be specified within the final
standard, along with the expected interaction of operator new() in the
presence of a new handler. (Does new() loop? It's not required anywhere!)

					Tony Hansen
				att!pegasus!hansen, attmail!tony
				    hansen@pegasus.att.com