Rony G. Flatscher

+1 Very nice, you seem to be a master of vim syntax files, kudos!

Hi Simon, thank you very much for sharing your rexx.vim! Skimmed over it and it is great that you have updated it (intended to do that myself, but alas, not enough free time at my hands at the moment). One little remark ad rexxEndDirective: by default "::END" must be spelled exactly like that (no blanks, all in uppercase) and must start in column 1. Something like syn region rexxIllegalEndDirective start="^\s*:\s*:\s*end\>" end="\ze\(\s\|;\|$\)" syn region rexxEndDirective start="^::END\C\>" end="\ze\(\s\|;\|$\)"...

20260426 Releasing ooRexx 5.2.0, moving branches/5.2.0 to releases/5.2.0

You may want to try nmake nsis_template_installer which works for me. Here a few pointerss (both files located i oorexx' main/trunk): CMake-build-readme.txt-68- To build the interpreter, you still use the nmake command. Once you have CMake-build-readme.txt-69- built, you can create the installer by issuing CMake-build-readme.txt-70- CMake-build-readme.txt:71: nmake nsis_template_installer CMake-build-readme.txt-72- CMake-build-readme.txt-73- We do not use the CPack command on Windows. and CMakeLists.txt-2089-...

20260420 A few version-related corrections.

Yes, that is to be expected, as the bug was not caught in 4.2, but got fixed in 5.x. However, I would assume/speculate that it could be fixed such, that the programs run without an error on 4.2 and 5.x. Again, if you want, you can send me your programs or a link to a zip archive and I look into it to come up with suggestions of how to fix it.

Graham, I can understand your frustration, however, please understand the core of the problem here: the program you have required "circular2.rex" has not yet been loaded, it is in the process of loading. Therefore it is not (yet) possible to refer safely to all of its public classes and routines. Each ::requires in a required program will immediately stall the loading of the program by resolving the required one first. In your circular requiring neither circular2.rex nor circular3.rex were loaded...

Hi Graham, here Rick's answer: Solely by accident an it was not working correctly because of the initialization problem. While working on 5.0.0 I discovered that the code that was supposed to detect that condition was not actually working. I corrected that. It only seemed to be working on 4.2.0, but there were all sorts of underlying problems. When the second package loaded, all of the initializations from the first file were not yet complete, because the first step of loading is to resolve the ::REQUIRES....