6 May
2008
6 May
'08
6:42 a.m.
"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. Anthony -- Anthony Williams | Just Software Solutions Ltd Custom Software Development | http://www.justsoftwaresolutions.co.uk Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL