From -1557582856054367741 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,4bcb385f3c23e7d9 X-Google-Attributes: gidf78e5,public From: fjh@mundook.cs.mu.OZ.AU (Fergus Henderson) Subject: Re: Seg fault with cout and cerr streams on SGI Date: 1997/04/09 Message-ID: <5if6t2$c7v@mulga.cs.mu.OZ.AU>#1/1 X-Deja-AN: 231902628 References: <5hjl1e$oak@netlab.cs.rpi.edu> <5hoouj$9ld@netlab.cs.rpi.edu> <5i1vl0$esq@mulga.cs.mu.OZ.AU> X-Original-Date: 9 Apr 1997 04:45:22 GMT Organization: Comp Sci, University of Melbourne X-Auth: PGPMoose V1.1 PGP comp.std.c++ Newsgroups: comp.std.c++ Originator: austern@isolde.mti.sgi.com James Kanze writes: >fjh@mundook.cs.mu.OZ.AU (Fergus Henderson) writes: > >|> Summary: the status quo in the DWP is fine. > >Yes and no. Agreed. The status quo is fine for the example at the start of this thread, but not for all examples. The status quo in the DWP is not very satisfactory for the operator new calls memset() example. >... there are significant grey areas as >to what functions really are safe in operator new, from a practical >point of view. Yes, agreed. >I can live with the status quo. Sure, just don't redefine the global operator new! -- Fergus Henderson | "I have always known that the pursuit WWW: | of excellence is a lethal habit" PGP: finger fjh@128.250.37.3 | -- the last words of T. S. Garp. --- [ comp.std.c++ is moderated. To submit articles: Try just posting with your newsreader. If that fails, use mailto:std-c++@ncar.ucar.edu comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html Comments? mailto:std-c++-request@ncar.ucar.edu ]