id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
4083	thread_id value not exported.	Michael Soliman. <boost@…>	Anthony Williams	"Moin Moin.

Trying to write programmes, using unique ids per thread and only per thread, recommend  themselves to be numbered by this_thread:get_id().
Unfortunately, the data-member (in ""boost\boost\thread\detail\thread.hpp"":line 50.) is both.:
0. declared private (not protected),
1. not exported by an access-function.
Right now, in order to maintain maximum compatibility as well as the emission of the same old error-messages, I just added the missing access-functions.:
const	thread_data&const_Wert(void)const{return	thread_data;};	
	thread_data&	  Wert(void)	  {return	thread_data;};	
Similarly I moved ""typedef ... super_t;"" in ""boost\boost\iterator\filter_iterator.hpp"":line 50 to the public-scope, as I needed it for my typedefs and did not see a point in deplaring any typedef as an unpublican(ian)^n (for an appropriate n>=0).

Hence my request to.:
a. generally use the keyword private only iff public/protected access-functions-to the underlying data exist.
b. To put typedefs in the public/protected area only, or at least to put typedefs in there, allowing acces to all types that might be needed (somewhen.).
b. To typedef all template-parameters like class Predicate, class Iterator in the aforementioned ""filter_iterator.hpp"", where, later on I did write a less restricted version of this class (But did not invest the same amount of work, just to add some access-functions.).

		Tschuess,
			Michael.
P.S.: I did append the ammended version of ""Filter_iterator"" in order to illustrate, what I meant (sorry for the partly German names.).
P^2.S.: As I am not a ""TeX""-guy, does anyone know how to switch off the superspript mode..
"	Feature Requests	closed	Boost 1.43.0	thread	Boost 1.42.0	Optimization	wontfix	access, functions, public, protected	boost@…