Re: xkcd: CrowdStrike

On 7/25/2024 10:59 AM, Paul S Person wrote:

On Wed, 24 Jul 2024 16:02:22 -0500, Lynn McGuire
<lynnmcguire5@gmail.com> wrote:
 

On 7/24/2024 12:39 PM, Paul S Person wrote:
...

I did have to block a program I compile myself, generally at least
once a day, from Microsoft Defender because it flagged it:
>
6/16/23 (Severe – Quarantined):
Detected: Trojan:Win32/Sabsik.FL.B!ml
file: C:\ow\ow\bld\wgml\win32\wgml.exe
>
It was doing this sort of thing with a /lot/ of files that hadn't been
changed or recompiled for a long long time, but I didn't bother with
blocking those. It's not presently doing this, so apparently it was
"false positive" problem. Perhaps someone thought that a particular
executable file header was unique to viruses.

>
Are you still working on Open Watcom ?  I am desperately trying to move
off it to a modern Fortran and C++ compiler setup with an integrated
IDE.  My port is not going well.

 I am working on implementing wgml, a related product Open Watcom uses
to produce its documentation but which we have only in 16-bit extended
DOS and 32-bit OS/2 with no source code. So I working on the source
code we created to get it to work the way the original does so the
docs will look the same as they do now.
 Michal has done some stuff on OW as such within the last few months,
so /some/ work is being done. But porting your code is probably a good
idea, a statement I regret having to make.
 I am sorry about your port and hope you can find solutions.

The real problem is that Fortran changed significantly from F66 / F77 to F90 and beyond.  I have written my own program to do most of the upgrades for me but I am subject to the old 80 / 20 rule.  It is easy to automate 80% of the work but the last 20% is dadgum hard to automate.  I am also cleaning up some old code from the 1970s that is problematic.
The real impetus is that I cannot debug my OW F77 code on Windows 10 / 11.  So every time time I or a customer runs into a bug, I have to use my Windows 7 Pro x64 PC.  Pain in the buttocks.  Both of my programmers still use Windows 7 for that reason.
I am porting to Microsoft Visual C++ and Intel Visual Fortran.  IVF is a very strict compiler and I hesitate to turn that strictness off.  In addition, the synergy between MSVC++ and IVF is ... lacking ... in several areas.  It was much better in the distant past but I have a habit of finding bugs in the IVF compiler that take them quite a while to fix.
I started off porting my F66 / F77 code to C++ using a very modified version of F2C.  Due to the complexity of input and output between the two languages (Fortran is record oriented, C is byte oriented), I have split the project into two parts as my customers need a x64 version of my software.
I did not know that Michal is still working on OW.  I have gotten a lot of help from Michal and Jiri over the years in fixing OW compiler bugs (mostly in the runtime library).
Lynn