|
Tom wrote: >Would having only one procedure in each module be a strategy? Unfortunately for us, the word 'thread' has been in common use in the AS/400 arena for a while. In this context, it means 'job', as in 'multi-threaded job queue' allows multiple jobs to process simultaneously. The discussion at hand is about Unix threads, which are parallel processes running in the same job. Imagine having an application that loads up a dozen arrays, sorts them and then prints them out. You could conceptually spawn 12 threads from your program where each thread loads an array and sorts it. As each thread completes, it has to notify the main thread that it is complete. Then the main thread prints the arrays. All in one program, all parallel tasks. --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.