As a life-long unabashed fan of Trace, I can see that anyone doing
non-trivial multithreaded Rexx programming would need far more
information than 'Trace I' can provide. However, the sheer volume of
information necessary seems to present no universally acceptable
format to interactively deal with such complexity.
Could we not define Mike's "basic-multithreading" Trace format as an
interactive trace option, and have another mechanism that writes
Rony's "multithread-the-world" Trace information to another
device/file for formatting as desired?
The latter would not be an "interactive" trace per se, but perhaps it
would help to narrow the scope of the problem. Not unlike sprinkling
a couple of SNAP dumps in your Assembler, in order to determine the
point at which you want to take an ABEND dump.
-Chip-
RIP: Les Kohler
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
