On 10/9/08, Roland Mainz <[EMAIL PROTECTED]> wrote: > Andrew Clarke wrote: > [CC:'ing [EMAIL PROTECTED] since the original > threads discussion comes from there (long ago)] > > > On Thu, 09 Oct 2008 09:30, Roland Mainz wrote: > > > Andrew Clarke wrote: > > > > On Thu, 09 Oct 2008 00:36, I. Szczesniak wrote: > > > > > On 9/29/08, David Korn <[EMAIL PROTECTED]> wrote: > > > > > > Subject: Re: ksh93t and version numbering (Was Re: [ast-users] > > > > > > ksh93t 2008-09-26 beta src) If I make a version that works with > > > > > > multiple threads, then it would become a new version like 'u'. > > > > > > > > > > Supporting multiple threads would be a feature which would be greatly > > > > > appreciated. > > > > > > > > Ummmm, that's called "pipelines" and "co-processes" isn't it? > > > > > > No, that are seperate "processes". The idea David was talking about is > > > to allow multiple execution threads in one process - the threads all > > > share the shell's global variables but have private local variables > > > which they can use for parallel processing. > > > > > > > Heh yes, I know the real differences. However I've had success exploiting > > co-processes in the past, albiet with a lot of brow-knitting coping with > > the management of connections through the obscure <&p, >&p and associated > > operators. > > > > From your next paragraph, it sounds like some real thought has been put > into > > the idea - would that be true? > > > Yes, technically the whole design now sits in my head and we only need > to implement it step my step, starting with the |sh|-->|shp| cleanup and > checking which libast APIs are not threadsafe (the Sun Studio compiler > have matching tools to find problems with thread race conditions).
Roland, do you have a list of required changes? Irek _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
