On 05/19/2014 01:58 AM, user wrote: > > I seem to have bumped into a vicious circle with threads. > > I want to "parallelize" a generator procedure producing a VARYING number of > results every call, in a sequence that is NOT important. > >>From the docs I understand that the usual method would be: > > every [(GEN) do] put(L1,thread put(L2,gen()))
You're putting a sequence of threads into L1, where each thread is putting results from gen() into L2. So L2 is the sequence of results you're interested in? I assume you're going to do a 'every wait(!L1)' to wait for all the results to get loaded into L2, right? What are the symptoms you're seeing? Did you make L2 thread-safe? > with GEN preferably generating the exact number of (varying) iterations as any > call of gen() would produce in results. I have trouble understanding this. Can you give a short, concrete, example? > The obvious solution would be to lose the "(GEN) do" but then only ONE THREAD > GETS CREATED ! Yep - that's expected. -- Steve Wampler -- [email protected] The gods that smiled on your birth are now laughing out loud. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Unicon-group mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unicon-group
