Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!bacchus.pa.dec.com!deccrl!decvax.dec.com!zinn!nuucp From: mjv@objects.mv.com (Michael J. Vilot) Newsgroups: comp.std.c++ Subject: Re: set_new_handler() and standardization Message-ID: <874@zinn.MV.COM> Date: 21 Aug 90 01:40:05 GMT Sender: nuucp@zinn.MV.COM Lines: 26 Tony Hansen writes: > ... E&S does NOT deal with library issues at all ... > The exact contents of need to be specified within the final standard In some ways, the standardization of the ANSI C++ library is more of a challenge than the language itself. The hardest part is that the availability of templates and exceptions will eventually change what we think is reasonable in a C++ library's design. If we assume exceptions are part of the standard, we may find the _new_handler approach is inappropriate. On the other hand, if we end up with an exception specification which has undesirable characteristics when running out of free heap and/or stack space, we'll need to retain this alternate approach. Of course, we can't decide yet -- exceptions are not part of the standard, and it will be some time before we have enough feedback from whatever scheme we adopt. It's certainly appropriate that E&S does not deal with library issues -- we clearly need a lot more experience and discussion before we're in a position to ``standardize existing practice.'' -- Mike Vilot, ObjectWare Inc, Nashua NH mjv@objects.mv.com (UUCP: ...!decvax!zinn!objects!mjv)