Michael Del Solio

Now, we have some more functions available: >>SOURCE FREE IDENTIFICATION DIVISION. PROGRAM-ID. GFXDEMO. DATA DIVISION. WORKING-STORAGE SECTION. 78 C-BLACK VALUE 0. 78 C-BLUE VALUE 1. 78 C-GREEN VALUE 2. 78 C-CYAN VALUE 3. 78 C-RED VALUE 4. 78 C-MAGENTA VALUE 5. 78 C-BROWN VALUE 6. 78 C-LIGHTGRAY VALUE 7. 78 C-DARKGRAY VALUE 8. 78 C-LIGHTBLUE VALUE 9. 78 C-LIGHTGREEN VALUE 10. 78 C-LIGHTCYAN VALUE 11. 78 C-LIGHTRED VALUE 12. 78 C-LIGHTMAGENTA VALUE 13. 78 C-YELLOW VALUE 14. 78 C-WHITE VALUE 15. 01...

Ok, I think we are on the good way with winbgm/putpixel() on SuperBOL-AIO-distribution :-) 1) Library (always check it with virustotal.com) and graphics.h from: https://github.com/dbautsch/winbgim/releases/tag/6.0a 2) Rename libbgi64.a to libbgi.a and put it into: C:\Users\YOURUSER\AppData\Local\GnuCOBOL\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0 3) Put graphics.h (from the Source Code ZIP file) into: C:\Users\YOURUSER\AppData\Local\GnuCOBOL\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0\include 4) Compile...

Ok, I think we are on the good way with winbgm/putpixel() on SuperBOL-AIO-distribution :-) 1) Library (always check it with virustotal.com) and graphics.h from: https://github.com/dbautsch/winbgim/releases/tag/6.0a 2) Rename libbgi64.a to libbgi.a and put it into: C:\Users\YOURUSER\AppData\Local\GnuCOBOL\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0 3) Put graphics.h (from the Source Code ZIP file) into: C:\Users\YOURUSER\AppData\Local\GnuCOBOL\mingw64\lib\gcc\x86_64-w64-mingw32\13.2.0\include 4) Compile...

Thank you very much. I searched now for a 64-bit version and found this one for MinGW: https://github.com/dbautsch/winbgim/releases/tag/6.0a The binary libbgi64.a looks ok while checked with virustotal (please recheck if you want to use it). We need to extract the graphics.h from the file "Source code (zip)" and put it into include folder of the SuperBOL-installation ... and we need to put ibbgi64.a into the libs folder... Tomorrow (or within the next days) I will try to compile the example from...

Some hints I found to this topic: putpixel() is part of the Borland BGI Graphics emulation (based on https://en.wikipedia.org/wiki/Borland_Graphics_Interface ): https://winbgim.codecutter.org/ But unfortunately this is just für MinGW-32 and so it does not work with the SuperBOL-distribution which is shipped with MinGW-64. It should work with the distribution of Arnold because this is based on MinGW-32 but this comes without g++ (C++ compiler). But g++ ist needed because in the graphics.h the file...

Thank you very much. Additional finding with Hex Editor-Plugin (VSCode) after converting/reconverting: The issue seems to occur specifically when Ctrl+Z (0x1A) follows a CR (0x0D) without a trailing LF (0x0A). Working file ending: CR LF SUB Failing file ending: CR SUB c:\_Share\Bug-Report-SUB-EOF>cobc -x HELLO-OK.cob HELLO-OK.cob:1: warning: ignoring unknown directive: '@OPTIONS MAIN' [-Wothers] 1 > 000020 @OPTIONS MAIN 2 | 000021 Identification Division. 3 | 000030 Program-Id. Hello. c:\_Share\Bug-Report-SUB-EOF>cobc...

Thank you very much. Additional finding with Hex Editor-Plugin (VSCode): The issue seems to occur specifically when Ctrl+Z (0x1A) follows a CR (0x0D) without a trailing LF (0x0A). Working file ending: CR LF SUB Failing file ending: CR SUB c:\_Share\Bug-Report-SUB-EOF>cobc -x HELLO-OK.cob HELLO-OK.cob:1: warning: ignoring unknown directive: '@OPTIONS MAIN' [-Wothers] 1 > 000020 @OPTIONS MAIN 2 | 000021 Identification Division. 3 | 000030 Program-Id. Hello. c:\_Share\Bug-Report-SUB-EOF>cobc -x HELLO-NOK.cob...

cobc enters infinite loop when compiling source files containing Ctrl+Z (ASCII 26) EOF marker on Windows