From 1084845577144174534
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,df4db449f12da465
X-Google-Attributes: gidf78e5,public
From: "John Hickin" <hickin@nortelnetworks.com>
Subject: Re: set_new_handler
Date: 2000/05/12
Message-ID: <391BFD09.E8F50C48@nortelnetworks.com>#1/1
X-Deja-AN: 622552418
Content-Transfer-Encoding: 7bit
Approved: Fergus Henderson <fjh@cs.mu.oz.au>, moderator of comp.std.c++
References: <39193150.6863D1F6@tesco.net> <391A17A6.5AF70EF7@wizard.net> <391AB9D2.207A3F05@physik.tu-muenchen.de>
X-Accept-Language: en
X-Authentication-Warning: bcarh8ab.ca.nortel.com: news set sender to  hickin@nortelnetworks.com using -f
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@demon.net
X-Mail2News-Path: news.demon.net!mulga.cs.mu.oz.au
X-Trace: mail2news.demon.co.uk 958138630 mail2news:23603 mail2news mail2news.demon.co.uk
Organization: Nortel Networks Corporation
X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov)
Mime-Version: 1.0
Newsgroups: comp.std.c++

Christopher Eltschka wrote:
> 

> 
> You mean there are implementations where set_new_handler
> neither affects the whole process nor just the current thread?
> 

It would make sense to me, for example, if it worked like signal masks
in pthreads (new threads would inherit the new handler of the creating
thread). In this way, set_new_handler called in a thread could affect
the new handlers of other (as yet to be created) threads but not of the
whole process.

Regards, John.

---
[ 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              ]




