Greetings Moritz, Yes, excellent leverage use of Claude Code!
You said:
Some of the bugs are caused by ooRexx implementing synchronization primitives itself, and it seems we might want to switch to the ones in the stdlib instead.
So are the two call styles sort of equivalent, just that the one style causes the synchronization primitives, and the suggested style does not cause them? I am thankful, Michael Moritz Hoffmann wrote:
Patches are on GitHub: https://github.com/ooRexx/ooRexx/compare/master...antiguru:ooRexx:concurrency-dispatch-fixes I can commit them to the SVN tree; easier for me to develop on GitHub. M On Sun, Jul 26, 2026 at 3:10 PM Rony G. Flatscher <[email protected] <mailto:[email protected]>> wrote: Hi Moritz, On 25.07.2026 23:48, Moritz Hoffmann wrote: > I found a bunch of memory corruption bugs (or, really, Claude Code found them). I captured the > diagnosis in bug reports in SF, and I can post patches if there's interest. Some of the bugs are > caused by ooRexx implementing synchronization primitives itself, and it seems we might want to > switch to the ones in the stdlib instead. *WOW*! Please, post the patches that fix these subtle problems that yield the reported subtle bugs! Personally, I would also think that switching the "private" synchronization primitives to the stdlib ones would be sensible, as long as these can be used on all platforms (Windows, Linux, macOS). Just my two cents. Best regards ---rony _______________________________________________ Oorexx-devel mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Moritz Hoffmann; http://antiguru.de/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
-- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
