From -8019702048676218694 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,c1bcfcd8cebdbbe9 X-Google-Attributes: gidf78e5,public From: Darin Adler Subject: Re: set_new_handler Date: 2000/04/16 Message-ID: #1/1 X-Deja-AN: 611840153 X-Mail2News-Path: news.demon.net!mulga.cs.mu.oz.au Approved: Fergus Henderson , moderator of comp.std.c++ References: <38f5d4b2@news.microsoft.com> X-Trace: mail2news.demon.co.uk 955892994 mail2news:28428 mail2news mail2news.demon.co.uk Organization: Bent Spoon Software X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f User-Agent: MT-NewsWatcher/3.0 (PPC) Newsgroups: comp.std.c++ X-Complaints-To: abuse@demon.net In article <38f5d4b2@news.microsoft.com>, "Gil Shafriri" wrote: > Does calling set_new_handler affects the whole process on just the > calling thread ? The C++ standard does not mention threads at all. Any platform that has threads must extend the standard to define how the library works with threads. So this is a platform question, not a C++ standard question. My guess is that most platforms would have set_new_handle affect the entire process, just because they would not address the issue at all in the library implementaitn. -- Darin --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html ]