Re: [Boost-build] no matching thread constructor using boost_thread built with STLport

Subject: Re: [Boost-build] no matching thread constructor using boost_thread built with STLport
From: Vicente Botet (vicente.botet_at_[hidden])
Date: 2012-04-17 06:27:45

Damjan Zemljič wrote
> 
> Yes, here it is:
> thread* thread_group::create_thread(const function0<void>& threadfunc)
> {
>     // No scoped_lock required here since the only "shared data" that's
>     // modified here occurs inside add_thread which does scoped_lock.
>     std::auto_ptr<thread> thrd(new thread(threadfunc));
>     add_thread(thrd.get());
>     return thrd.release();
> }
> 
> 

I was thinking you check with something like

' U
_ZN5boost6threadC1ERKNS_9function0IvN8stlp_std9allocatorINS_13function_baseEEEEE'

Is it usual that compiler generates the code that passes the allocator
along with the parameter passed? (I'm total newbie this regard)

I guess the std::allocator should be the default in boost::function.

Best,
Vicenet

--
View this message in context: http://boost.2283326.n4.nabble.com/no-matching-thread-constructor-using-boost-thread-built-with-STLport-tp4561861p4564311.html
Sent from the Boost - Build mailing list archive at Nabble.com.