Re: [Boost-users] [Boost.Thread] Scheduling

From: Patrick Loney (Patrick.Loney_at_[hidden])
Date: 2008-08-11 11:33:02

>> Friendly advice: get a good book on multi-threaded programming before
proceeding with your project.

> Any suggestions?

>> The condition variable should be signaled _before_ the lock is
unlocked, otherwise you have a race condition upon which causes the
signal to get lost.

> Is this definitely the case and please can you describe the error in
more detail (or provide a link... or tell me to read the book...)

Got it, the condition can be lost in the code to handle spurious wake
ups... still like any suggestions about books though.

******************************************************************************

"This message and any attachments are solely for the intended recipient and may contain confidential and privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you."

Interactive Transaction Solutions Ltd (2473364 England)

Registered Office: 
Systems House, 
Station Approach
Emsworth PO10 7PW

**********************************************************************

Ce message électronique contient des informations confidentielles à l'usage unique des destinataires indiqués, personnes physiques ou morales. Si vous n'êtes pas le destinataire voulu, toute divulgation, copie, ou diffusion ou toute autre utilisation de ces informations, est interdite. Si vous avez reçu ce message électronique par erreur, nous vous remercions d'en avertir son expéditeur immédiatement par email et de détruire ce message ainsi que les éléments attachés.

Interactive transaction Solutions SAS- France (RCS Pontoise : 489 397 877)

Siège social :
Parc Saint Christophe, 
10, Avenue de l’Entreprise
95865 Cergy-Pontoise Cedex

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________