Dom Wise

Thanks Jeremy. I just picked boolean extension as an example of a possible alternative to creating a new class method in case it was demed easier to implement or preferable from a design standpoint. The basic protocol i.e. "open, read/write then close the file in a single line" is what I would like to see as a programmer and I don't mind if it's implmented as a class method (for which there is now an RFE - thanks Rony), an extension to an existing method using e.g. string or boolean, or something...

Firstly, kudos (to all concerned) for getting the YAML parser implemented in such a short timeframe! I'd certainly support the ability to close files when performing bulk reads or writes. As well as adding class methods it seems there's also the option of extending the existing instance methods with an optional 'close' parameter but anything which allows auto-close with arrayIn/Out is really nice because it makes it possible to read/write an entire file in a single line of code. For example, with...

Is there a use case from 858/ 859 where it's necessary to override values already set by an ::OPTIONS directive in a package with "global" options or is it always sufficient to just allow defaults to be specified to be used only when a specific option is not already set by the package ? In this scenario GlobalOptions (or perhaps DefaultOptions) "TRACE...." will only take effect for a package if there is not already an ::OPTION TRACE directive in that package I ask because I've tried the patch (thanks...

Thank you very much Rony. From a quick scan of the code it looks like a switch to be applied to all package options at once which works for me. It's possible a use case for more granular application of this option may exist (i.e. only block TRACE from being overridden instead of all options) but for me it's fine. I'm busy with Christmas preparations right now so will build and test it once I have some spare time, perphaps in a day or two.

Great stuff! From: bugs@oorexx.p.re.sourceforge.net bugs@oorexx.p.re.sourceforge.net On Behalf Of Gil Barmwater Sent: 14 December 2025 13:29 To: [oorexx:bugs] 2041@bugs.oorexx.p.re.sourceforge.net Subject: [oorexx:bugs] #2041 Crash when specifying only -O or -OG on the command line for Rexx.exe Good morning! I believe I know the cause of the problem and how to fix it and plan to work on it later today. Stay tuned! [bugs:#2041] https://sourceforge.net/p/oorexx/bugs/2041/ Crash when specifying only...

Excellent! Thank you for the update

Packages should be able to block GlobalOptions requests

Yes, please get to bed, it's late! I should do the same :) For tomorrow (or after): The pause is likely Windows processing the crash (perhaps writing a dump file). If you check the Windows Event Log (Windows Logs -> Application and filter for Errors) you should see a crash event reported Linux /Mac etc may actually report "segmentation fault" if they have the same problem with the rexx binary but I haven't looked at those yet I'd say this is low priority since it's a contrived scenario that you would...