Boost C++ Libraries: Ticket #4083: thread_id value not exported.

attachment set

Sat, 10 Apr 2010 13:01:23 GMT

attachment → fi.h.gz

I did append the ammended version of "Filter_iterator" in order to illustrate, what I meant (sorry for the partly German names.).

cc set

Sat, 10 Apr 2010 13:26:19 GMT

cc boost@… added

P^{3_.S.: Cut & Paste errors prevail.
The access-functions should be.:
const detail::thread_data_ptr&const_Wert(void)const{return thread_data;};}

detail::thread_data_ptr& Wert( void) {return thread_data;};

, of course. _Tschuess, Michael.

status changed; resolution set

Anthony Williams — Mon, 07 Jun 2010 08:55:05 GMT

status new → closed
resolution → wontfix

The details of thread::id are private for a purpose. The internal contents are not intended for public consumption, and providing such access would break encapsulation.

thread::id is suitable for use as a key in an associative container, so can be used directly as e.g. a map index.

status changed; resolution deleted

Tue, 08 Jun 2010 10:15:11 GMT

status closed → reopened
resolution wontfix

Moin Moin. Ok.: "not intended for public consumption" does mean, that the authors did not have the plan to do so. My proposal now implies, that a sensible application to do so arose and can be satisfied without removing any degrees of implementing future functionality from the authors' sphere of influence. My proposal just contains

status changed; resolution set

Anthony Williams — Tue, 08 Jun 2010 21:37:09 GMT

status reopened → closed
resolution → wontfix

I disagree that a sensible application for exposing the internals of thread::id has arisen.

I will not be changing thread::id to expose the internals. If you wish to use thread::id as an index, create an associative container such as std::map<boost::thread::id,some_data>.

Wed, 09 Jun 2010 13:36:43 GMT

Moin Moin.

I disagree that a sensible application for exposing the internals of thread::id has arisen.

Hm. Sorry, I did not mean to be pert. My intention was just to remove a circumventable restriction. As it is a small change, I shall be implementing it within the sources all by myself at anytime I am using a new distribution.

Tschuess,

Michael.