Return-Path: Received: from mx04.mrf.mail.rcn.net ([207.172.4.53] [207.172.4.53]) by mta05.mrf.mail.rcn.net with ESMTP id <20020403160106.EMCB19155.mta05.mrf.mail.rcn.net@mx04.mrf.mail.rcn.net>; Wed, 3 Apr 2002 11:01:06 -0500 Received: from milliways.osl.iu.edu ([129.79.245.239]) by mx04.mrf.mail.rcn.net with esmtp (Exim 3.35 #5) id 16snC5-0003g7-00 for david.abrahams@rcn.com; Wed, 03 Apr 2002 11:01:06 -0500 Received: from milliways.osl.iu.edu (localhost [127.0.0.1]) by milliways.osl.iu.edu (8.11.6/8.11.6/IUCS_2.44) with ESMTP id g33G10A24726; Wed, 3 Apr 2002 11:01:00 -0500 Received: from mta414.mail.yahoo.com (mta414.mail.yahoo.com [216.136.128.66]) by milliways.osl.iu.edu (8.11.6/8.11.6/IUCS_2.44) with SMTP id g33G02A24708 for ; Wed, 3 Apr 2002 11:00:03 -0500 Date: Wed, 3 Apr 2002 11:00:03 -0500 Message-Id: <200204031600.g33G02A24708@milliways.osl.iu.edu> From: MAILER-DAEMON@yahoo.com To: boost-admin@lists.boost.org X-Loop: MAILER-DAEMON@yahoo.com Subject: Delivery failure Sender: boost-owner@lists.boost.org Errors-To: boost-owner@lists.boost.org X-BeenThere: boost@lists.boost.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Boost mailing list List-Unsubscribe: , List-Archive: Message from yahoo.com. Unable to deliver message to the following address(es). : Sorry your message to cresus22@yahoo.com cannot be delivered. This account has been disabled or discontinued. : Sorry your message to jjb700@yahoo.com cannot be delivered. This account has been disabled or discontinued. --- Original message follows. X-Track: 1: 40 Return-Path: Received: from milliways.osl.iu.edu (129.79.245.239) by mta414.mail.yahoo.com with SMTP; 03 Apr 2002 07:59:49 -0800 (PST) Received: from milliways.osl.iu.edu (localhost [127.0.0.1]) by milliways.osl.iu.edu (8.11.6/8.11.6/IUCS_2.44) with ESMTP id g33EduA22960; Wed, 3 Apr 2002 09:39:56 -0500 Received: from mail2.commerzbank.com (mail2.commerzbank.com [212.149.48.101]) by milliways.osl.iu.edu (8.11.6/8.11.6/IUCS_2.44) with ESMTP id g33EciA22890 for ; Wed, 3 Apr 2002 09:38:44 -0500 Received: from sv016317.exchange.commerzbank.com (sendmail.commerzbank.com [172.16.71.150]) by mail2.commerzbank.com (Commerzbank Mail-System) with ESMTP id 38105116C for ; Wed, 3 Apr 2002 16:35:15 +0200 (CEST) Received: by sv016317.exchange.commerzbank.com with Internet Mail Service (5.5.2653.19) id <2GBLGLD2>; Wed, 3 Apr 2002 16:37:33 +0200 Message-ID: From: "Hoeffner, Detlef" To: "'boost@lists.boost.org'" Subject: RE: [boost] Thread locals MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: boost-admin@lists.boost.org Errors-To: boost-admin@lists.boost.org X-BeenThere: boost@lists.boost.org X-Mailman-Version: 2.0.8 Precedence: bulk Reply-To: boost@lists.boost.org List-Help: List-Post: List-Subscribe: , List-Id: Boost mailing list List-Unsubscribe: , List-Archive: Date: Wed, 3 Apr 2002 16:37:41 +0200 > As a substitute, try using the comparison operator for the boost::thread > class. This can fill the gap in many (but not all) cases where you are > managing the set of threads yourself. I need this mainly for tracing purposes in spots where I have no knowledge of the current instance of thread. This does not seem to help me in that case. > On some platforms (i.e. pthreads), the "thread_id" is actually an opaque > type (pthread_t) rather than a numeric value, and I think that is why no > such operation is exposed in the current version of the library. It is however possible to provide a class threadid, that has dependent on the platform different members but provides operations as ==, !=, operator<<(ostream&, ), ... That would be fine to solve the problem. Regards Detlef -----Original Message----- From: Moore, Dave [mailto:dmoore@ashtontechgroup.com] Sent: Mittwoch, 3. April 2002 14:33 To: 'boost@lists.boost.org' Subject: RE: [boost] Thread locals > -----Original Message----- > From: Hoeffner, Detlef > [mailto:Detlef.Hoeffner@partner.commerzbank.com] > Sent: Wednesday, April 03, 2002 6:59 AM > To: 'boost@lists.boost.org' > Subject: [boost] Thread locals > > > Hello all, > > I am replacing my thread abstraction with the thread package > from boost. It > is very nice but I am missing two things. > > The first is the possibility to get an identifier for the > current thread, a > thread id. As a substitute, try using the comparison operator for the boost::thread class. This can fill the gap in many (but not all) cases where you are managing the set of threads yourself. On some platforms (i.e. pthreads), the "thread_id" is actually an opaque type (pthread_t) rather than a numeric value, and I think that is why no such operation is exposed in the current version of the library. Regards, Dave _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost .