yahoo_04.txt [plain text]

Date: Wed, 3 Apr 2002 09:44:37 -0500
Message-Id: <200204031444.g33EibA23012@milliways.osl.iu.edu>
From: MAILER-DAEMON@yahoo.com
To: boost-admin@lists.boost.org
Subject: Delivery failure
Sender: boost-owner@lists.boost.org
Errors-To: boost-owner@lists.boost.org
Precedence: bulk

Message from yahoo.com.
Unable to deliver message to the following address(es).

<agarciamartiartu@yahoo.es>:
Sorry, your message to agarciamartiartu@yahoo.es cannot be delivered.  This account is over quota.

<open00now@yahoo.co.uk>:
Sorry, your message to open00now@yahoo.co.uk cannot be delivered.  This account is over quota.

--- Original message follows.

X-Track: 0: 100
Return-Path: <boost-admin@lists.boost.org>
Received: from milliways.osl.iu.edu (129.79.245.239)
  by mta468.mail.yahoo.com with SMTP; 03 Apr 2002 06:44:13 -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 g33EgcA22988;
	Wed, 3 Apr 2002 09:42:38 -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 <boost@lists.boost.org>; 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 <boost@lists.boost.org>; 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: <CD3F0650BD65D31191BF0008C75D8DBD0300F66F@SV018443>
From: "Hoeffner, Detlef" <Detlef.Hoeffner@partner.commerzbank.com>
To: "'boost@lists.boost.org'" <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: <mailto:boost-request@lists.boost.org?subject=help>
List-Post: <mailto:boost@lists.boost.org>
List-Subscribe: <http://lists.boost.org/mailman/listinfo.cgi/boost>,
	<mailto:boost-request@lists.boost.org?subject=subscribe>
List-Id: Boost mailing list <boost.lists.boost.org>
List-Unsubscribe: <http://lists.boost.org/mailman/listinfo.cgi/boost>,
	<mailto:boost-request@lists.boost.org?subject=unsubscribe>
List-Archive: <http://lists.boost.org/MailArchives/boost/>
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
.