All access to the standard handles are done via Stream object instances, and all of the methods are guarded so the synchronization between threads is automatic. I'm not sure what you are asking with the last question.
Rick On Fri, Jan 21, 2022 at 9:31 AM rvjan...@xs4all.nl <rvjan...@xs4all.nl> wrote: > Hi, > > Some questions: > > Can anybody point me to the relevant source code that shows how ooRexx > ‘handles’ (no pun intended) multithreaded access to file handles; more > specificly (and also) how the access to the standard shell handles is > guarded (if at all) in the case multiple threads want to use stdin, stdout > and stderr. I seem to remember that *say* can be rerouted: are the > handles protected at that moment? > > In NetRexx these handles are static, so cause a bit of trouble when we > re-route in a heavily multithreaded environment/application like Pipelines. > The JSR223 interface suffers likewise, as it seems to require that every > thread going through it can assign its own file handles. > > Also, what happens when we ‘address’ an external environment - do all > threads assume their own I/O handles, or are they using the same set that > is set centrally? > > Many thanks in advance. > > René. > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
