Hi Rony, On the first one I don’t really have an opinion, except that we should avoid the patch going stale. On the second one: it should be a welcome addition, but I doubt we really need it now. Reasons:
- Not a fan of fat binaries: they tend to stay fat until unsupported - ooRexx currently builds fine (and fast!) on M1 - there should be a decision on what to distribute. Personally, I would be fine with a Mac distribution for X86_64 and another for ARM64/aarch64 - we have separate Windows distributions also, and in fact it would be great if someone built it for Power on the Mac because not everybody I know got rid of those. We probably also need future differences in Apple OS versions due to the ever-annoying additional security work they are doing: save file - do you give the application you are using access to your disk? Yes/no - can you authenticate yourself (again)? Another favourite is the quarantine-bit: you are opening an application (really?) that you downloaded from the internet (really? Did I?). Do you want to put it in the bin? But: that is no reason not to integrate the patch with the option. Would be great if Enrico would do that … but if he does not feel like it, maybe P.O. can have a look. Best regards, René. > On 14 Sep 2021, at 18:18, Rony G. Flatscher <rony.flatsc...@wu.ac.at> wrote: > > 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/> > <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 > 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
