Parallel Index Search: use of Jobs.WaitForJobs

[GoogleCodeExporter]

Why do we wait for a finished job using
while iFounder=0 do Sleep(0);

Wouldn't Jobs.WaitForJobs(false, INFINITE); be better?

I tried this and it didn't work. (returned immediately with fail code).

P.S. Bouncing balls working well (classic version might need some work).

Original issue reported on code.google.com by wayne.sc...@gmail.com on 29 Jun 2009 at 3:30

[GoogleCodeExporter]

fixed r20

Original comment by saraivag...@gmail.com on 29 Jun 2009 at 2:14

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Wayne, sorry for the late feedback and thanks for send theses issues and 
questions.

Recently I can't do some tests on the published code, cuz I'm out of time every 
day
almost. Thats is the reason for some pieces of the code some times need better 
approachs.

Thanks again for using PJ in other circumstances, the main project that uses
paralleljobs is a ARU(audio response unit in a callcenter program) and the way 
it
works don't use the new parts of the code only the basic parallelism provide on 
the
firsts versions.

Original comment by saraivag...@gmail.com on 30 Jun 2009 at 11:45

• Added labels: ****
• Removed labels: ****