Activity: Talk or presentation › Science to science
Description
Writing powerful multithreaded programs is very easy in ooRexx. However, debugging multithreaded programs with the Rexx TRACE keyword instruction and the peer TRACE() built-in function is difficult and sometimes almost impossible because of missing concurrent related execution information while tracing. This presentation will introduce the problem description, the situation with ooRexx 5.0 and a proposal for ooRexx 5.1 to enable full debugging of the most dynamic and complex multithreaded Rexx programs. The proposal tries to follow the Rexx language design to keep the language easy and small, yet, allow access to the necessary information.