As long as there is no architecture review board (ARB) in effect and developers
in "land under
water" mode that hinders them to communicate, I would like to apply the classic
rule: "silence
counts as approval" for the following planned changes/patches:
* concurrency trace: this is a tested, important feature as it is for the
first time that one
becomes able to really trace concurrently executing Rexx programs; this is
especially helpful
for students who learn programming and must apply their acquired skills
also in mastering
concurrently executing Rexx programs (e.g. when debugging GUI applications
from awt/swing and/or
JavaFX); in this context also the documentation needs to be supplemented
which I would do (in
the area of the existing RXTRACE section in rexxref.pdf), RFE with patch:
<https://sourceforge.net/p/oorexx/feature-requests/794/>,
* extract and commit the CMake definitions from Enrico's patch to allow
ooRexx on MacOS to be
optionally built as a universal binary such that ooRexx can run with the
same binary on Intel
and M1 computers.
Will wait at least a week such that there is enough time for consideration and
communication.
---rony
P.S.: Also, if time permits (unfortunately I am also in "land under water" mode
myself) I would like
to add the ability to create "stick"-versions of ooRexx, such that up-to-date
versions can be
created each time ooRexx gets compiled.
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
