----- Original Message ----- From: "Anthony Williams" <anthony_w.geo@yahoo.com> To: <boost@lists.boost.org> Sent: Tuesday, May 06, 2008 8:42 AM Subject: Re: [boost] Review Request: future library (N2561/Williams version)
"vicente.botet" <vicente.botet@wanadoo.fr> writes:
why we don't need to protect get_future() function of multiple thread access?
By design you can only call this function once, so if multiple threads called it concurrently and that was safe, only one would get the future, and the other would get an exception. The user should therefore use appropriate synchronization to ensure correct results anyway, so making this call thread-safe would not be of benefit.
I don't understand the need of this function. Could you show a use case for promise::get_future() function? _____________________ Vicente Juan Botet Escriba