Dear Rony, I made a patch request some time ago
https://sourceforge.net/p/oorexx/patches/207/ <https://sourceforge.net/p/oorexx/patches/207/> That is necessary for running the samples test cases on macOS (and *nix to I think). I have written test cases for all samples and also amended the list of test cases. I have documented all changes that are needed and if you follow the link above there is further link to my Dropbox where the bulk of the work is sitting, waiting to be included. Read these two files and compare to the Appendix B you just brushed up: "What is here.txt" "Changes to CMakeLists.txt and other remarks for making testGroups for samples.txt" For information: some of the test cases are asynchronous and fail to complete in the right order every now and then (philfork is one such example), one might need to have a less strict testing for such samples, but in principle all samples have a test case. Where it was possible I tested two ways: expected output against actual output and the other way around, so getting to much or to little output would be captured. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 10.03.2020 um 19:34 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>: > > In order not to start with editing the class tree section ("Chapter 4. The > Basics of Classes") > before some time has gone by to be able to object about the planned content, > I turned to the samples > section ("Appendix B. Sample Rexx Programs") which took quite some work to > iron it out (obsolete > scripts, quite a lot missing scripts, commented out oodialog samples that for > some reasons were > left-over). > > Here the temporary URL for the resulting "rexxpg.pdf": > <https://www.dropbox.com/sh/gxvvgskb04gdsqf/AACRo_ZLeFOdoBXUHroPY_-Ca?dl=0>. > > So I would appreciate it if you could take some time and read through > Appendix B and if you find > errors and/or have better wordings, explanations to come up with them such > that ideally I just need > to copy and paste them. This would be of real value and help! > > Also, feedback on the formatting of that section is appreciated (the script > names are now in the > case as found on the file system and marked up with the code-tag), would it > be o.k. this way? > > [BTW, I think we should go over the ole/apps samples as applications like > Lotus WordPro etc. may not > be deployed anymore. At least there should be a meaningful error message if > they crash, because the > Lotus apps are not installed. Also, it may make sense to place a "parse pull > ." at the end of the > scripts in case they got run via the Explorer (GUI) interface as the Rexx > scripts would open and > immediately close upon return or error. Also, the MS Access samples should be > adapted and tested, > the used Jet engine, I think, is still only available in 32-bit, maybe MS has > a 64- to 32-bit bridge.] > > ---rony > > P.S.: Will try to get back to chapter 4 ASAP, but also need to address other > burning issues (like > the students now are locked out of our Universities and we need to come up > with some sort of remote > lecturing, quite chaotic at the moment, meetings, etc.). > > > > _______________________________________________ > 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
