On 26.07.2026 16:28, 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.
Maybe this would be very helpful as then we could see how the testsuite works on all platforms
including BSD. If possible also your C++ test should be incorporated in the native tests of the
testsuite such that it gets run on all platforms as well.
Then seeing the test results we should be able to assess the commit. If there are unexpected
side-effects it would be possible to revoke the commit until they could be analyzed and fixed as well.
Just my 2 cents.
It would be interesting to learn what others think.
---rony
On Sun, Jul 26, 2026 at 3:10 PM Rony G. Flatscher <[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]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
