Greetings Jean Louis,
Jean Louis Faucher wrote:
The point 2 is for P.O..
Here, we have a "normal" number of warnings:
ooRexx-macOS10-X86_64-build5 warnings
ooRexx-macOS15-X86_64-build10 warnings
ooRexx-macOS26-M4-build5 warnings
ooRexx-FreeBSD14-build10 warnings
ooRexx-NetBSD10-build2 warnings
ooRexx-OpenBSD7-build7 warnings
ooRexx-OpenIndiana-build2 warnings
ooRexx-OpenSuse15-build2 warnings
ooRexx-RaspberryPiOS32-build2 warnings
ooRexx-RaspberryPiOS64-build2 warnings
ooRexx-Solaris11-build2 warnungs
oorexx-ubuntu16-build2 warnings
ooRexx-windows10_32-build2 warnings
ooRexx-windows10_64-build1 warning
ooRexx-windows11_32-build2 warnings
ooRexx-windows11_64-build1 warning
ooRexx-windows32-build2 warnings
ooRexx-windows64-build1 warning
ooRexx-windows7_32-build2 warnings
ooRexx-windows7_64-build1 warning
ooRexx-windows8_32-build2 warnings
ooRexx-windows8_64-build1 warning
Here, we have a bunch of new warnings after the concurrency rework:
warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
ooRexx-ArchLinux-buildaround 60 warnings, segmentation fault
ooRexx-CentOS10-buildaround 160 warnings
ooRexx-Controller-Ubuntu-buildaround 80 warnings
ooRexx-Debian12-buildaround 80 warnings
ooRexx-Fedora43-buildaround 60 warnings
ooRexx-linux-aarch64-buildaround 35 warnings
ooRexx-LinuxMint22-buildaround 80 warnings
ooRexx-Manjaro-buildaround 60 warnings, segmentation fault
ooRexx-Ubuntu22-buildaround 70 warnings
ooRexx-Ubuntu24-buildaround 80 warnings
(snip)
THAT type of example list is wonderful! As someone who's best programming language is Rexx / ooRexx, then any time the Rexx interpreter gripes at me it is a very big deal that I must change the code
to deal with. I am NOT comfortable seeing "warning" that is safe to just ignore.
I am thankful,
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
